Tilman Vogel

Lack of `DELETE` makes it impossible to use `pg_net` to clean up supabase storage objects in `UPDATE`/`DELETE` Postgres triggers. Or am I missing something?

My workaround: ``` root@gw:~# cat /etc/hotplug.d/iface/99-omcproxy #!/bin/sh case "$ACTION" in ifup|ifdown) /etc/init.d/omcproxy restart ;; esac ```

> this is already automatically by `Realtime.Database.detect_ip_version/1` and we already run it in production with IPv6 > > is your use case not covered by this? Right, that only buys...

> we'll also need to update the mix.exs file to bump up the version 👀 How do you handle the versions? I have updated it before but obviously, it's a...

Ah, by the way, a similar issue appears with `verifyOtp()` even though, here, the JSON in fact looks like: ``` {"code":"otp_expired","message":"Token has expired or is invalid"} ``` but still, the...

Could it be that the API version check fails because GoTrue is not exposing the version header to the script, see: https://github.com/supabase/auth/blob/06464c013571253d1f18f7ae5e840826c4bd84a7/internal/api/api.go#L331

Sorry, I had forgotten my inquiry about this and actually, I am currently not using any captive portal system, so while I very much agree on the S-curve observation, I...

> FYI, you are probably best to use something else (`sh` maybe). I have #22 open (maintains python 2.7 support) and someone else has #21 (basically the same as yours,...

> That's always been the behaviour. It returns postgres' query outcome rather than user data. Arbitrarily storing user data in the cron.job_run_details table is probably not a good idea. That...

Ah, good that this is already in the works! However, the fix to default it to "global" is questionable to me because that is a string that in general gets...