Threads
Loading user profile...
Mandar Joshi raises a concern about potential bugs in static after-create.sql scripts for PostgreSQL extensions, suggesting a validation step to prevent issues like the pgmq overloaded drop_queue fix. Edward Song agrees, proposing a lightweight validation focused on install and upgrade behavior, with optional static checks for hardcoded function signatures.
Mandar Joshi proposes enhancing the self-hosted developer experience in Supabase Studio. The suggestion focuses on improving workflows such as migrations, generated types, and observability for self-hosted users. The proposal includes a capability-based model to manage UI visibility and suggests starting with observability and diagnostics as a first step. Mandar seeks feedback on whether this direction is useful for contribution.
@UsmanGhias This is a private project issue, not a confirmed Supabase bug. You haven’t shown the actual function definitions, logs, or test output, so the proposed fix is just guesswork. Please confirm the cause before suggesting a patch.
@sharonerez2205-rgb Could you share the RPC definitions and the actual 404/500 error messages or logs? I’d like to try reproducing this locally.
Hey! Looks like this was caused by a temporary issue on Supabase’s side. They had an internal change that broke JWT verification for Dashboard sessions, which is why the login events weren’t being recorded and the permissions weren’t loading properly. The good news is they’ve already reverted the change and fixed the issue. Your actual project and database weren’t affected. (here's the status page: https://status.supabase.com/incidents/vfb32z24wt64).