nrainer-materialize

@morsapaes: Yes, the OOM can still be reproduced! I migrated and added this check to the bounded-memory framework in https://github.com/MaterializeInc/materialize/pull/26845. Since it fails (even with a higher memory specification), I...

@vmarcos: Is there anything we can and need to do about this or are we awaiting https://github.com/MaterializeInc/materialize/issues/20442?

I have just seen that it is not a customer environment but the production sandbox.

We got this today in Nightly in [QA Canary Environment Base Load](https://buildkite.com/materialize/nightlies/builds/6289#018d69d1-dd6e-45d8-ab6a-6b189f041174). Let me see if it is reproducible...

> We got this today in Nightly in [QA Canary Environment Base Load](https://buildkite.com/materialize/nightlies/builds/6289#018d69d1-dd6e-45d8-ab6a-6b189f041174). Let me see if it is reproducible... Yes, it is reliably reproducible!

This is still observed in PROD with `0.97.3` in `88f4bc01-67b2-4ae7-b53e-6c264993152c-0` (production sandbox): https://materializeinc.sentry.io/issues/4299987926

Further occurrence: https://buildkite.com/materialize/tests/builds/72839#018cf7a5-a7f1-4ea7-940e-f1285977da2c

Very similar issue in the same job in https://buildkite.com/materialize/nightlies/builds/6860#018e326e-6f0f-4561-a6b8-4feb05d8efe5: ``` 8:1: error: non-matching rows: expected: [["four"], ["one"], ["three"], ["two"]] got: [["four"], ["one"], ["three"], ["two"], ["two"]] Poor diff: + two |...

@ParkMyCar, this is still a draft, but does it make sense so far?

["Full testdrive in cloudtests" in nightly](https://buildkite.com/materialize/nightly/builds/7630#018f3efa-1552-4119-8425-1ab1e48b555c) reports: ``` testdrive/fivetran-destination.td:22:1: error: connecting to fivetran destination: transport error: error trying to connect: tcp connect error: Connection refused (os error 111): tcp connect...