fix(snapshots): Show 'Waiting for base' instead of 'Base' when base artifact not found#115446
Merged
Merged
Conversation
…ha exists but base artifact not found
github-actions
Bot
added
Scope: Frontend
Contributor
|
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
mtopo27
approved these changes
May 12, 2026
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.50% |
…l type The comparison_state field was being set to "waiting_for_base" but the Pydantic Literal type only allowed "pending", "processing", "success", and "failed", which would cause a ValidationError at runtime. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 57342fa. Configure here.
…exists When a comparison record exists in PENDING/PROCESSING/FAILED state, the base artifact was already found. Showing "waiting_for_base" in that case is misleading — fall through to "solo" and let the run_info carry the actual comparison state. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
NicoHinderling
added a commit
that referenced
this pull request
May 12, 2026
…ng base (#115448) When a head snapshot uploads before its base build (e.g., due to network timing), the status check task immediately posts a FAILURE to GitHub with "No base snapshots found." This is a false negative — the base just hasn't arrived yet. This adds a grace period: instead of failing immediately, the task posts an IN_PROGRESS status ("Waiting for base snapshots...") and schedules a delayed self-invocation (10 minutes). If the base arrives before the timeout, the existing comparison flow re-triggers the status check which takes the normal path — the timeout task becomes a harmless no-op. If the base never arrives, the timeout flips it to FAILURE. The approach is event-driven rather than poll-based: no retries, no new state to maintain. The task re-runs the same idempotent logic and queries the DB for current truth. Companion to #115446 which adds the matching "Waiting for base" UI state in the frontend. --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
When a snapshot is uploaded with a
base_shabut no matching base artifact exists yet, both the snapshot list and detail pages incorrectly show a "Base" badge — implying the build is a base build with no comparison intended. In reality, the upload explicitly requested a comparison but the base hasn't been uploaded yet.This changes both the list and detail APIs to return a
waiting_for_basestate whenbase_shais present but no base artifact or comparison exists. The frontend now shows a "Waiting for base" tag with a tooltip explaining the build will resolve within ~10 minutes or fail.Backend:
comparison_type): returns"waiting_for_base"instead of"solo"whenbase_shaexists but no comparison manifest foundcomparison_state): returns"waiting_for_base"instead ofnullwhenbase_shaexists but noPreprodSnapshotComparisonrecord foundSnapshotComparisonInfoPydantic model: added"waiting_for_base"to thecomparison_stateLiteral type to preventValidationErrorat runtimeFrontend:
<Tag variant="muted">Waiting for base</Tag>with tooltipisSoloViewtreatswaiting_for_basethe same assolofor rendering purposes