Noel Kwan

> The issue on insert will be fixed by https://github.com/risingwavelabs/risingwave/pull/7202. Seems like not fixed yet, will continue investigating along with https://github.com/risingwavelabs/risingwave/issues/7189#issuecomment-1371846545. ```sql dev=> CREATE TABLE t (data struct[]); INSERT INTO...

Encounters `stack overflow` error.

Ready for review.

Hi @yezizp2012, looks like the tests are failing, could you PTAL? Thanks! cc @huangjw806, only after this is merged in, then we should cut a new release for 1.7.0-standalone.

Here's my local errors when starting it: ``` cargo build --bin risingwave ./target/debug/risingwave ``` log ``` 2024-02-28T23:34:08.04622+08:00 INFO rw-main risingwave_common::telemetry::report: start telemetry reporting thread 'rw-main' panicked at src/meta/src/barrier/recovery.rs:348:14: clean dirty...

> > Hi @yezizp2012, looks like the tests are failing, could you PTAL? Thanks! > > Looks like the single node test passed in the ci workflow? > > >...

``` 2024-02-27T16:22:45.072413567Z WARN risingwave_stream::executor::dml: txn_id=4294967296 Too many chunks for atomicity. Sent them to the downstream anyway. thread 'rw-compaction' panicked at /risingwave/src/storage/hummock_sdk/src/key.rs:1047:21: key UserKey { 1004, TableKey { 0000008558294d8b000000 } }...

> Is there any recent change to the test itself? I saw that the test can still pass [yesterday](https://buildkite.com/risingwavelabs/main-cron/builds/1896). I checked the diff commits and didn't see any suspicious changes....

Can you add some comments on the motivation behind this PR?

Need to figure out: 1. Why e2e test will TLE. (Perhaps it's the `get_row` each time we persist state in debug mode). 2. Why deterministic test `test_high_barrier_latency_cancel` takes a long...