What changed
supabase/tests/public-model-timeouts.test.mjs: the New York fall-back check now uses its own model (model-dst), and its two rows are inserted inside the transaction that the check already rolls back.
Why
The verify job fails on every branch today with DST fixtures are inside the frozen window: 5 !== 2.
The check freezes the overview's clock at 2026-11-03 12:00 UTC and expects only its two rows (1 Nov) in the 5-day window. But the other model-a fixtures are dated from the real clock. From 29 Oct, three of them fall inside that frozen window too.
The two fall-back rows also stayed in the table after the check. Once 1 Nov has passed, they would fall inside later checks' windows.
How
- The fall-back rows and a
model-dstcatalogue row are inserted afterbegin, and both queries ask formodel-dst. - The existing
rollbackremoves the rows again. - Nothing else in the test or schema changes.
Before and after
| Before | After | |
|---|---|---|
verify from 29 Oct to early November | Fails (5 !== 2) | Passes |
| Fall-back rows after the check | Kept, dated 1 Nov | Rolled back |
Verification
PGLITE_MODULE=…/pglite/dist/index.js node supabase/tests/public-model-timeouts.test.mjs:
- On main: fails with the same assertion as CI.
- On this branch: "Public model timeout regression tests passed: output parity, grants and indexed model selection."
Model: Claude Opus 5.5 (xhigh effort) · Harness: Claude Code in T3 Code
🤖 Generated with Claude Code
Activity
6WARNING
Review limit reached
You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
Next included review available in 41 minutes.
View limit details
Limit details: You’ve used the included review currently available.
Review configuration:
Run configuration
- Source mode: Auto
- Repository: Unavailable
- Branch: Unavailable
- File: No configuration file from this repository applied
- Commit: Unavailable
- Layers: defaults
- Review profile: CHILL
- Plan: Advanced
- Run ID:
453e38e7-c66c-4f99-92ff-49de96b6587f
Commits
Reviewing files that changed from the base of the PR and between d2404167b9cb49b9d146eb1dba8d01ce0e071a30 and 602a3154dbae1bc7cad16eb20634fa5a7f0da6da.
Files selected for processing: 1
supabase/tests/public-model-timeouts.test.mjs
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
-
- (https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)
- Mastodon
Comment @coderabbitai help to get the list of available commands.
Codex Review Summary
This comment shows the latest Codex review activity on this pull request.
| Review | Status | Commit | Review trigger |
|---|---|---|---|
| 📝 Code Review | ✅ Completed 2026-10-29T17:45:58.877333Z | 602a315 | PR opened |
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review" or "@codex security review".
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.
The latest updates on your projects. Learn more about Vercel for GitHub.