Dennis Felsing

This is still happening: https://buildkite.com/materialize/nightlies/builds/6468#018dad49-70eb-493a-8f90-89326e1a1bfc

I scanned all test runs in CI in the last 2 weeks to see if this is still happening. It actually happened again on Saturday: https://buildkite.com/materialize/nightlies/builds/6598#018ddaa1-ae42-4d54-97a3-72fcac31ea5a ``` Core was generated...

I managed to reproduce this (once so far) on my dev server, which is x86-64, so it's not longer an aarch64 migration blocker! ``` [10484465.596861] timely:work-4[2804728]: segfault at 7f584d651948 ip...

I think that's expected. I think I remember it's the time on server, not race time.

I guess we still want this? Sorry for waking up late, can you rebase?

``` SELECT COUNT(DISTINCT c_name) FROM qa_canary_environment.public_tpch.tpch_q18 WHERE o_orderdate >= '2023-01-01'; Error: Evaluation error: internal error: Non-positive multiplicity in DistinctBy ``` on https://console.materialize.com/regions/aws-us-east-1/shell, @petrosagg anything we need to provide? This is...

This is the QA Release Verification env: https://www.notion.so/QA-Release-Verification-107e03aaf4fe4029a35c21c46009f8fb The Mz environment was recreated about two weeks ago and had no problems since then. With the upgrade to v0.96.2 this issue...

Sure, will try. Edit: Updated to 15.6 now. Will try to remove the filter in Sentry and let's see if this reoccurs. Edit2: so far so good

Still occurring after all, do I need to recreate the source?

Seems good now for this source. I removed the filter in Sentry and no new occurrences so far.