fix: report repository refresh failures and reject busy updates - #841
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7ada28f9e3
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c41a00137
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Repository refresh requests could hang during an active operation, and the dashboard could report success after a refresh ended in an error. API failures could also appear without an explanation because the dashboard read the wrong response field.
Return HTTP 409 for refreshes during preparation, queueing, download, removal, or expiration, after checking ownership. Show API and polling failures, and report refresh success only when the repository reaches
ready.Related to #834. This fixes reproducible refresh and feedback bugs; the specific production restoration failure still needs repository status and logs, so this PR does not close the issue.
Validation: 48 focused tests passed, including restoration with an unchanged commit and preservation of the repository ID. Changed backend/test files passed ESLint; the browser bundle compiled. Full TypeScript checking reports existing errors in unchanged files.