Fix regression batch processing - #2497
Conversation
6ab0b59 to
fd749a8
Compare
![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: fd749a81b2
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 24fe0e5c22
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 56d86e1237
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f27306f4c2
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 19db9598aa
ℹ️ 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".
niemyjski
changed the title
niemyjski
changed the title
niemyjski
left a comment
niemyjski
left a comment
There was a problem hiding this comment.
Addressed all current review feedback in d185d57. The PR now contains only the regression batch continue fix and its canonical integration coverage; the broad 5xx redirect and saved-view prompt changes are fully removed.
|
1 participant
Summary
User impact
A fixed stack with no regression candidate no longer prevents a later fixed stack in the same batch from being marked as regressed. Existing API status-page routing remains unchanged: only status 0, 408, and 503 trigger recovery.
Verification
d185d57b08eac2e4831ab06a1762bb7ee7bcc5a9origin/mainat24d6ad72a6659eec918c4655b531c099208912da; branch is 0 commits behinddotnet build tests/Exceptionless.Tests/Exceptionless.Tests.csproj --no-restore— passed with 0 warnings and 0 errorstest-apiexecuted the integration suite successfully in 5m55stest-client,test-e2e,docker-build,version, and CLA checks passed on the exact headgit diff --check origin/main...HEAD— passedReview
origin/main...HEAD— no blocking findingsNotes
The broad 5xx redirect was originally inferred from the reported intermittent site-wide 500 errors. That inference was incorrect for client routing: ordinary API 500 responses must not redirect to the status page, so the change was fully backed out.