Repository navigation
fix: History error handling and Discovery request races - #4
Merged
Merged
Conversation
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.
History now reads HTTP status, retryAt and request receipts directly, so busy responses are not described as exhausted anonymous quota. Discovery claims the initial request before POST returns and ignores stale starts after a repository switch; long partial-history warnings wrap and scroll on narrow screens.
The change preserves the accepted UI, graph semantics and API contracts. A targeted offline browser regression covers structured errors, duplicate starts, late responses, failure recovery and 390/430px readers; it is included in test:stale. The existing motion test now exercises the real provider response-byte limit and task receipt instead of synthesizing HTTP 503 plus a machine-coded error string; every existing assertion is retained.
Validation: independent code review found no actionable defects. Local typecheck, build, 67 targeted unit tests, 15 new browser checks and existing History/loading, navigation, stale-response, unified-workspace and motion acceptance passed with offline fixtures in Chromium. Both ARM64 PR workflows passed on final HEAD
41a21e471a426bbcf58a0563d9c8685aa31c9498: M2 PR validation and P0/P0.5 stable UI validation, including ordinary Private Beta, trusted TLS/Caddy staging and unchanged build digest checks.Separate Live CI diagnosis: the earlier main run failed on api.github.com connection timeouts before analysis assertions. Its single retry passed all 7 live tests and the ARM64 build/container checks: https://github.com/yunmin311/GitLineage/actions/runs/39095285950/attempts/2 . This is evidence for baseline main, distinct from this PR's offline/browser checks.
No production deployment or restart is part of this PR.