As an initial step, could we introduce some sort of log warning,
metric or other indicator for operators to determine if they're
running with a non-UTF-8 encoding?
On Mon, Nov 28, 2022 at 1:21 PM David Capwell wrote:
>
> It probably has to be done on a case-by-case basis
>
>
> Yeah, this is what
*Hi everyone,An update on the current CFP process for Cassandra
Summit. There are currently 23 talk submissions which are far behind what
we need. Two days of tracks mean we need 60 approved talks. Ideally, we
need over 100 submitted to ensure we have a good pool of quality talks. We
already have q
So much awesome here. Big +1 to having checkstyle be the source of truth.
On 2022/11/24 17:10:28 Maxim Muzafarov wrote:
> Hello everyone,
>
>
> First of all, thank you all for this awesome project which I have
> often been inspired by. My name is Maxim Muzafarov I'm a Committer and
> PMC of Ap
I'm going to +1 what Stefan has said. I've heard on many occasions from
newcomers to the project that having to use Ant is a deterrent. As a matter
of fact, a few weeks ago, I spent a Sunday afternoon helping somebody
trying to build Cassandra and Ant caused a ton of problems. "Ok. ant really
super
> The test build of Cassandra 4.1.0 is available.
Our requirements for 4.1-rc were one green CI run. And no regression
flakies (except the two we have waivers for).
Three consecutive jdk8 and jdk11 circleci runs can be found in these lists:
jdk8
https://app.circleci.com/pipelines/github/michaels
