Wojtek Majewski

Yes please! I just stumbled upon this error when fiddling with Supabase's Declarative Schemas: https://github.com/supabase/cli/issues/3483 **migra** also is unable to properly handle this :-(

Yes please!!!

@lauri865 as a temporary workaround i managed to create an awk script to colorise the output, the results look much better:  Use the script like this: ```shell supabase db...

I confirm this issue - it manifests every time a code fences are present.

Hey @jahnavisana2812, I'm not a supavisor developer but working on problems with abrupt connection closures and pool saturation in my app. Maybe my findings would be helpful for you: ###...

Hey! @adbl I'm using pgmq in my Supabase-dedicated workflow engine [pgflow](https://pgflow.dev) and i ship a backported **read_with_poll** to include the fixes from the issue you linked (but with small changes...

You can do what I did in pgflow and just back port read_with_poll into a new schema. You can copy the code I linked as it is compatible with 1.4.4...

Yup seems like it was updated in https://github.com/supabase/postgres/pull/1668 Now lets make sure [pgflow.dev](https://pgflow.dev/) works with this update...

I observe the same behaviour. I'm on 2.0.73. I store my commands in separate repo and symlink them: ```shell ❯ ls -l .claude/commands/restack.md lrwxrwxrwx - jumski 19 gru 07:52 .claude/commands/restack.md...

Have the same issue on 2.0.29: ``` > use cloud install command to downgrade version 2.0.28 ⎿  API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.44.custom.input_schema: input_schema does not support oneOf, allOf, or anyOf at...