We were able to narrow it down, and it seems that both issues have been
introduced by [1] (both tests pass without this commit). There is a preliminary
fix, and we're working on a minimal repro. Please track [2] for more
information and latest updates.
[1]
2023 11:40
> To: dev@cassandra.apache.org
> Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra
> 5.0-alpha2)
>
> NetApp Security WARNING: This is an external email. Do not click links or
> open attachments unless you recognize the sender and know the content is
>
The link is fixed. Thanks!
From: Miklosovic, Stefan
Sent: Monday, November 6, 2023 11:42
To: dev@cassandra.apache.org
Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)
I can't view it either
I can't view it either.
From: guo Maxwell
Sent: Monday, November 6, 2023 11:40
To: dev@cassandra.apache.org
Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)
NetApp Security WARNING: This is an external email. Do not click
Do I need permission to view this link? When I open it, an error appears,
saying “It may have been deleted or you don't have permission to view it.”
Benjamin Lerer 于2023年11月6日周一 18:34写道：
> I created a Dashboard to track the progress and remaining tasks for 5.0:
>
I created a Dashboard to track the progress and remaining tasks for 5.0:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=593
Everybody logged in should have access. Ping me if it is not the case.
Le sam. 4 nov. 2023 à 19:54, Mick Semb Wever a écrit :
>
> Please mark such bugs
Please mark such bugs with fixVersion 5.0-beta
If there are no more tickets that need API changes (i.e. those that should
be marked fixVersion 5.0-alpha) this then indicates we do not need a
5.0-alpha3 release and can focus towards 5.0-beta1 (regardless of having
blockers open to it).
Appreciate
Yep, data loss bugs are not any old bug. I’m concretely -1 (binding) releasing a beta with one that’s either under investigation or confirmed.As Scott says, hopefully it won’t come to that - the joy of deterministic testing is this should be straightforward to triage.On 4 Nov 2023, at 17:30, C.
I’d happily be the first to vote -1(nb) on a release containing a known and reproducible bug that can result in data loss or an incorrect response to a query. And I certainly wouldn’t run it.Since we have a programmatic repro within just a few seconds, this should not take long to root-cause.On
> I think before we cut a beta we need to have diagnosed and fixed 18993
> (assuming it is a bug).
Before a beta? I could see that for rc or GA definitely, but having a known
(especially non-regressive) data loss bug in a beta seems like it's compatible
with the guarantees we're providing for
Totally agree with the others. Such an issue on its own should be a
priority in any release. Looking forward to the reproduction test mentioned
on the ticket.
Thanks to Alex for his work on harry!
On Sat, 4 Nov 2023 at 12:47, Benedict wrote:
> Alex can confirm but I think it actually turns out
Alex can confirm but I think it actually turns out to be a new bug in 5.0, but
either way we should not cut a release with such a serious potential known
issue.
> On 4 Nov 2023, at 16:18, J. D. Jordan wrote:
>
> Sounds like 18993 is not a regression in 5.0? But present in 4.1 as well?
> So
Sounds like 18993 is not a regression in 5.0? But present in 4.1 as well? So I
would say we should fix it with the highest priority and get a new 4.1.x
released. Blocking 5.0 beta voting is a secondary issue to me if we have a
“data not being returned” issue in an existing release?
> On Nov
I agree and just now opened it for 5.0-beta (among others.)
Kind Regards,
Brandon
On Sat, Nov 4, 2023 at 11:08 AM Benedict wrote:
>
> I think before we cut a beta we need to have diagnosed and fixed 18993
> (assuming it is a bug).
>
> > On 4 Nov 2023, at 16:04, Mick Semb Wever wrote:
> >
> >
I think before we cut a beta we need to have diagnosed and fixed 18993
(assuming it is a bug).
> On 4 Nov 2023, at 16:04, Mick Semb Wever wrote:
>
>
>>
>> With the publication of this release I would like to switch the
>> default 'latest' docs on the website from 4.1 to 5.0. Are there any
15 matches
Mail list logo
