Repository navigation
feat(stovepipe): List open issues in pages - #924
Merged
Merged
Conversation
prathshenoy
force-pushed
the
codex/stovepipe-open-issue-list
branch
2 times, most recently
from
October 23, 2026 04:00
f99ace7 to
660c3e1
Compare
This was referenced Oct 23, 2026
prathshenoy
added this pull request to stack #927
October 23, 2026 14:28
prathshenoy
marked this pull request as ready for review
October 23, 2026 14:28
prathshenoy
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
October 23, 2026 14:28
prathshenoy
force-pushed
the
codex/stovepipe-open-issue-list
branch
from
October 23, 2026 16:32
660c3e1 to
1da0bcc
Compare
Base automatically changed from
codex/stovepipe-issue-history-storage
to
main
October 23, 2026 16:49
prathshenoy
force-pushed
the
codex/stovepipe-open-issue-list
branch
from
October 23, 2026 16:50
1da0bcc to
b189d84
Compare
mnoah1
reviewed
Oct 23, 2026
mnoah1
left a comment
mnoah1
left a comment
Contributor
There was a problem hiding this comment.
Let's use a similar materializer pattern to the request/queue summaries
mnoah1
approved these changes
Oct 23, 2026
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Persist immutable opening and resolution history, retaining the associated build and timestamp after an issue resolves or reopens. **Why**: - Preserve issue lifecycle history separately from current open issues and per-build observations, without enabling reconciliation or repair tracking yet. ## Test Plan - [x] Add unit tests. - [x] Verify history retention, duplicate replay, concurrent creation, and identifier boundaries against MySQL. ## Revert Plan - Revert this PR. No runtime writer 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#923 1. uber#924 1. uber#925
DivyanshGarg380
pushed a commit
to DivyanshGarg380/submitqueue
that referenced
this pull request
Oct 24, 2026
## Summary **What**: - Define queue-scoped notifications for new failure observations and successful final analysis, without enabling publishers or consumers. - Expose persisted failures for one build in bounded, cursor-based pages with required build and task identities. **Why**: - Prepare ordered issue reconciliation while keeping build polling independent and messages small, without adding tables or serialized failure collections. ## Test Plan - [x] Add unit tests. - [x] Verify pagination, queue/build isolation, byte-exact ordering, and identifier boundaries against MySQL. ## Revert Plan - Revert this PR. The contracts and reads are not wired into runtime workflows; no schema migration or data removal is required. ## Issue Links - [CODEM-607](https://linear.app/uber/issue/CODEM-607/build-analysis) ## Stack 1. uber#923 1. uber#924 1. uber#925
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