Conversation
… violation The manifest upsert returned the existing row's id via SetId, but the tag had already been created with the new (uninserted) uuid, causing a FK violation on every re-push. Fix: query for an existing manifest first; if found, reuse it and skip the insert so the tag always references a valid manifest id. Plain INSERT is restored for manifests — the check handles sequential re-pushes and the DB unique constraint handles true concurrent races. Tag upsert is kept so re-pushing a tag always updates to the latest manifest.
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
interface conversion: interface {} is uint32, not uintfollowed by a FK violationmanifest.GetId()(new UUID) beforeSaveChangesran; the manifest upsert returned the existing row's id viaSetId, leaving the tag referencing a UUID that was never insertedTest plan