We are working on a reliability scanner and Supabase was one of few opesource codebase we picked from GitHub. The idea was fairly simple, how stable is the code, what are the critical problem areas (if any) and what is the Production Reliability Score (PRI) for Supabase.
Interesting finding, a surprising number of identified problems were already reported by the community and fixed. Speaks volumes about the quality of Supabase.
But the problems clustered around cron jobs, scheduled webhooks and queues stood out as potential key problem areas:
A few examples:
The silent failures concerned me. The job can report success while the receiving system gets incomplete or corrupted data.
The header problem also required three separate fixes over roughly three months. Two fixes passed review and were merged, but the problem returned with different real-world inputs. CodeRabbit approved these PRs.
For a production sensitive product, I believe that there is some amount of fragility in the code where normal code review and test coverage seems to be failing.
Have cron jobs, scheduled webhooks or queues been a problem area for you? Or is this just a corner case(s)?
I do have 55 other issues detected that do not have a GitHub ticket filed as yet and your response will help me better assess the new issues. Thank you.
The user is evaluating Supabase's production reliability, focusing on cron jobs, scheduled webhooks, and queues. They found several issues, including header corruption and missing queue messages, which concern them due to silent failures. They seek community feedback on whether these are common problems or isolated cases.
No astroturfing or synthetic engagement. Posts and comments must reflect genuine human engagement. Content that exists primarily to manipulate sentiment, simulate community activity, or feed AI training pipelines will be removed.