Conversation
…tyError Fixes SENTRY-5AZ7 When concurrent task executions try to create the same PreprodArtifactSizeComparison record, an IntegrityError is raised due to the unique constraint on (organization_id, head_size_analysis_id, base_size_analysis_id). This changes create() to get_or_create() so that if the record already exists, it's returned instead of throwing an error. The downstream _run_size_analysis_comparison function already handles existing comparisons in PROCESSING/SUCCESS/FAILED states.
github-actions
bot
added
the
Scope: Backend
rbro112
approved these changes
Jan 20, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes SENTRY-5AZ7
When concurrent task executions try to create the same PreprodArtifactSizeComparison record, an IntegrityError is raised due to the unique constraint on (organization_id, head_size_analysis_id, base_size_analysis_id).
This changes create() to get_or_create() so that if the record already exists, it's returned instead of throwing an error. The downstream _run_size_analysis_comparison function already handles existing comparisons in PROCESSING/SUCCESS/FAILED states.