{{ message }}
Repository navigation
test(repo): retry stalled live updates and name stalled analytics polls - #7041
Merged
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews completed. Code inspection confirms Claude’s diagnostic nit: a failed update retry reports only the second attempt in the thrown error. Codex reported no findings. No blocking issues were identified.
Findings
Stats
Claude findings: 1 · Codex findings: 0 · Confirmed: 1 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
avallete
approved these changes
Oct 7, 2026
7ttp
enabled auto-merge
October 7, 2026 18:48
TFSebben
pushed a commit
to TFSebben/supabase_cli
that referenced
this pull request
Oct 23, 2026
## TL;DR re-issues the live `branches create` once when the platform rejects it because the database restarted mid-create - `branches list` (and `branches create` on `main` / `next`) failed with `unexpected create branch status 400: … FATAL: 57P01: terminating connection due to administrator command` (also seen as `the database system is shutting down`). the platform restarts the database it is configuring while the create is in flight. the shared live helper now recognises only that rejection, removes the half-made branch if it got listed, and re-issues the create once, the same way supabase#7041 handles the network restrictions stall. a second rejection still fails the test, and `create.live.test.ts` uses the same helper ## ref - spotted in: [branches list](https://github.com/supabase/cli/actions/runs/39221185565/job/117956603829) --- _Generated by [Claude Code](https://claude.ai/code/session_016f5jekWaBDRtATpEf65mtq)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
retries the network restrictions live update once when the platform stalls it, and makes the analytics poll say what stalled
network-restrictions updatefailed withexpected 1 to be +0and no stderr. the platform'sapplystalled until the harness killed the cli at the 60s exit guard. the update is now re-issued once when it was killed before printing its result, the same way the restore already retries, and a second stall fails naming the killthe Logflare stored id poll in
Owner.analyticsran out with a bareNoSuchElementErrorafter Analytics left healthy mid test. it now fails withNotStoredErrornaming the first or sentinel event, its id and the poll countref