Stefanos Mousafeiris

@samwillis the e2e was not flaky, the async event emitter change revealed a minor regression we had during the PG in the client integration where bytearrays were not being deserialized...

@barbalex just to confirm - you're getting this error with `createMany` but you are not getting it when creating the exact same rows with `create` one by one?

@barbalex could you check if this issue persists with `v0.10.x`? I'm wondering whether this is an issue related to https://github.com/electric-sql/electric/issues/1095 If it still persists, is there any chance you could...

I will be looking into this - for the time being I think that doing full reloads rather than hot reloads should work - you can disable fast refresh from...

@KyleAMathews might be worth renaming the issue to something like "Large TOASTable rows lead to crash loop" for easier lookup as we're probably not closing this soon. @alco would setting...

The issue seems to be that we are trying to transfer `ParserOptions` which contains anonymous functions to the worker without proper serialization. Either the parsing is done at the calling...

The issue as @samwillis mentioned is that JS JSONs will always get encoded as `JSON` type, not `JSONB`, as we can't know what it's meant to be encoded as from...

Hey, thank you for reporting! On what platform/engine are you facing this issue? We have a test covering this and I can't reproduce the issue on Node or Chromium -...

Hey @jgoux - could you confirm if this is still an issue and if so if you have a path to reproduce it?

Closing as no errors have been reported about this and am unable to reproduce + have test coverage! Feel free to reopen if you reproduce the errors though