Repository navigation
feat(stovepipe): Store currently open issues - #916
Merged
Merged
Conversation
This was referenced Oct 22, 2026
prathshenoy
added this pull request to stack #920
October 22, 2026 13:25
prathshenoy
force-pushed
the
codex/stovepipe-open-build-issue-storage
branch
2 times, most recently
from
October 22, 2026 15:21
3251029 to
76978d4
Compare
This was referenced Oct 22, 2026
prathshenoy
force-pushed
the
codex/stovepipe-open-build-issue-storage
branch
2 times, most recently
from
October 22, 2026 19:32
e0e302a to
9001fa5
Compare
prathshenoy
changed the title
prathshenoy
force-pushed
the
codex/stovepipe-open-build-issue-storage
branch
from
October 22, 2026 19:40
9001fa5 to
f2df069
Compare
mnoah1
approved these changes
Oct 22, 2026
prathshenoy
marked this pull request as ready for review
October 22, 2026 21:13
prathshenoy
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
October 22, 2026 21:13
prathshenoy
enabled stacked auto-merge
October 22, 2026 21:13
2 tasks done
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Persist individual validation issue observations per build and queue, with duplicate detection. **Why**: - Retain observed failures across polls and restarts without replacing earlier observations or rewriting serialized collections. ## Test Plan - [x] Add unit tests. - [x] Verify persistence against a real MySQL database. ## Revert Plan - Revert this PR. No runtime consumer is enabled; the additive table can remain unused without affecting validation. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis) ## Stack 1. uber#902 1. uber#907 1. uber#915 1. uber#909 1. uber#916
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Add periodic issue detection and durable observation recording, with a final pass after observing build completion. - Stop polling validations that end without a recorded build result and use normal queue retry handling for analysis failures. **Why**: - Accumulate validation failures before build completion and retry partial persistence without duplicating observations. ## Test Plan - [x] Add unit tests. ## Revert Plan - Revert this PR. No runtime wiring or schema changes are introduced, and existing build processing is unchanged. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis) ## Stack 1. uber#902 1. uber#907 1. uber#915 1. uber#909 1. uber#916
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Record one history event per build when analysis cannot complete, without rerunning detection or changing validation results. - Retry history recovery failures while acknowledging messages that cannot identify a valid build and request. **Why**: - Make potentially incomplete failure information visible without blocking validation or repeatedly querying the build provider. ## Test Plan - [x] Add unit tests. ## Revert Plan - Revert this PR. No runtime wiring or schema changes are introduced, so existing validation behavior is unchanged. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis) ## Stack 1. uber#902 1. uber#907 1. uber#915 1. uber#909 1. uber#916
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Connect build analysis to build-start and completion notifications, using a no-op detector in the reference service while keeping result recording independent. - Configure bounded analysis retries and connect dead-letter recovery that records incomplete analysis without rerunning detection. **Why**: - Keep result recording independent of issue detection while allowing deployments to provide real detection. ## Test Plan - [x] Add unit tests. - [x] Verify the reference service integration with its default detector. ## Revert Plan - Revert this PR. No schema changes need reversal, and existing observations can remain stored without affecting prior build processing. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis) ## Stack 1. uber#902 1. uber#907 1. uber#915 1. uber#909 1. uber#916
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.
Summary
What:
Why:
Test Plan
Revert Plan
Issue Links
Stack