[#1] Rendre l’ingestion de tickets atomique pour éliminer les doublons #1
Labels
No labels
confidence:High
confidence:Low
confidence:Medium
effort:L
effort:M
effort:S
horizon:later
horizon:next
horizon:now
impact:High
impact:Low
impact:Medium
kind:feature
kind:improvement
priority:P0
priority:P1
priority:P2
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AI/orchai#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
L’insertion des tickets repose sur un schéma read-then-write sans contrainte d’unicité DB. En cas de courses entre polling manuel et planifié, des doublons fonctionnels peuvent être créés.
Metadata
improvementP0nowMHighHighEvidence
Files
First slice
Ajouter un index UNIQUE (tracker_id, artifact_id), migrer insert_if_new vers INSERT OR IGNORE, puis adapter le retour pour détecter proprement l’insertion effective.