Conversation
added 8 commits
September 13, 2026 02:37
Consolidate the reviewed topic, preserving its runtime and regression assertions.
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.
Draft — depends on #1533. Files changed includes the foundation; incremental review shows only this PR's changes.
Summary
Bound monitoring work and distinguish executing SDR attempts from queued and remaining pipeline sectors.
Tookstarts at recorded currentDoentry, not posting or ownership. Pause and late responses cannot manufacture fresh elapsed time.Defaults remain pending preview
500and coalescing enabled, without sealing-specific priority or default pending hiding. This requires the parent's attempt schema/entry recording, not pacing or backend-health policy.Validation and limits
API normal/race, exact-tag vet/lint, frontend tests and offline Chromium validation. PostgreSQL query/handler fixtures cover transitions, missing/old/wrong tasks and query failure. Large-backlog fixtures include tens of thousands of waiting sectors linked to actual SDR task rows, plus multiple owners and running/preparing tasks. The summary query/mapper was also exercised on disposable Yugabyte 2025.2.2.2-b11 with the actual curio-schema migration runner.
These single-node cost samples are not production or multi-node performance proof; attributable retries were not measured. Execution-entry telemetry does not prove healthy native computation.
Review scope
Series overview. No dependency on the other children. Ready after the foundation is accepted, its duplicated diff is removed and applicable checks pass.
Own commits and comparison base
Own commits:
39ed163f752f377e90d1891970075a3964d320f4— web: show bounded current-attempt task snapshots13c36379deab17796e17e6846850c03e669db2e9— web: bound PoRep page queries and recover refresh statef7cb60769b4138035035d0bd7fc0a7ace98e38c3— web: distinguish SDR attempts from remaining pipeline sectors245b2c02e82667d0edc0f5e2fb58856be5d8a935— test: label overview fixture population and browser versioneba504dfeeee0f07c370fc877dec6dce548887e7— test: exercise large linked SDR summary populationsCumulative counts use upstream
86e95967cd602dbf8db5ea538abe986c3968e2e3; the incremental base is0c1f7cbd4dc9797e9773f1edd165af6b72d3fe27.