Repository navigation
feat(stovepipe): Add request issue lookups - #1025
Merged
Merged
Conversation
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 6, 2026 18:46
eb62fce to
dfd00a9
Compare
This was referenced Nov 6, 2026
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 6, 2026 19:25
dfd00a9 to
9d10e72
Compare
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 6, 2026 19:43
9d10e72 to
5da1c49
Compare
2 tasks done
prathshenoy
marked this pull request as ready for review
November 6, 2026 21:00
prathshenoy
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
November 6, 2026 21:00
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 6, 2026 21:33
5da1c49 to
edf3d6a
Compare
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 6, 2026 23:23
edf3d6a to
61949bd
Compare
mnoah1
approved these changes
Nov 9, 2026
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 9, 2026 14:00
61949bd to
965b515
Compare
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 9, 2026 14:14
965b515 to
fcac07a
Compare
prathshenoy
force-pushed
the
request-issues-api
branch
from
November 9, 2026 14:17
fcac07a to
1f13e94
Compare
prathshenoy
enabled stacked auto-merge
November 9, 2026 14:17
Tmwakalasya
pushed a commit
to Tmwakalasya/submitqueue
that referenced
this pull request
Nov 11, 2026
## Summary **What**: - Add paginated storage for request-level issue summaries. - Support conditional updates as a request's issue results advance. **Why**: - Provide an efficient way to list what a request introduced, encountered, or closed. Existing issue history is organized by issue rather than request, so reconstructing each request's results on every read would require scanning unrelated history. - Allow the materializer to retain a closure when an older opening or report is replayed later. Version-guarded replacements support that ordering without a transaction. ## Test Plan - [x] Add unit tests. - [x] Verify storage and conditional updates against a real database. ## Revert Plan - Revert dependent readers and materialization first, then this PR. The unused summary table can remain. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis-issue-track) ## Stack 1. uber#1023 1. uber#1027 1. uber#1024 1. uber#1025
Tmwakalasya
pushed a commit
to Tmwakalasya/submitqueue
that referenced
this pull request
Nov 11, 2026
## Summary **What**: - Extend issue history to retain repeat reports and original opening references. - Keep repeat reports from changing lifecycle status or transition timestamps. **Why**: - Retain evidence that later validation builds encountered an already-open issue. Those reports are needed for request-level existing results, but must not reopen an issue or move its transition timestamp. - Preserve the opening in each new event so replay can identify the occurrence after the issue has closed or reopened. Deploy the additive history column before updated consumers; existing lifecycle history remains readable without backfilling it. ## Test Plan - [x] Add unit tests. - [x] Verify event retention and queue isolation against a real database. ## Revert Plan - Revert dependent reporting and projection changes first, then this PR. Retained repeat-report events and the additive column can remain unused. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis-issue-track) ## Stack 1. uber#1023 1. uber#1027 1. uber#1024 1. uber#1025
Tmwakalasya
pushed a commit
to Tmwakalasya/submitqueue
that referenced
this pull request
Nov 11, 2026
## Summary **What**: - Generate request-level issue summaries from the shared issue history. - Record repeat reports during normal processing and dead-letter recovery. **Why**: - Keep request results consistent with accepted issue updates after failures. Retaining an event and repairing its projections before advancing the cursor lets normal processing and recovery finish interrupted writes without inventing reports. - Distinguish newly covered requests from historical requests whose issue summaries were never recorded. Recording coverage begins only after all issue-tracking workers use the updated contract. ## Test Plan - [x] Add unit tests. - [x] Verify replay rebuilds missing summaries against a real database. - [x] Verify stale workers cannot reopen issues or corrupt request results after recovery and a newer build. ## Revert Plan - Revert dependent request-result reads and this PR. Operational issue state and retained issue history remain available; summary rows can remain unused. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis-issue-track) ## Stack 1. uber#1023 1. uber#1027 1. uber#1024 1. uber#1025
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