fix(workers): filter releasedTentativeFaces to canonical UUIDs (ADR 0102) #1265
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/release-tentative-canonical-uuid"
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
Second live-G4 failure fix (job
604def57, 2026-10-16). The envelope contract-version fix (PR #1263) worked — this run got past that validation — but Core then rejected the submission with:Root cause: the enqueue exports
cio.occurrence_keyasfaceAnnotationId, and 15 of the owner's 388 tentative rows carry a generic_evidence-style<uuid>:0key. The worker passed them through the ADR 0102 release signal (releasedTentativeFaces), whose Core validator requires canonical UUIDs and rejects the whole submission otherwise.Fix (worker-side, minimal blast radius):
main.py:_CANONICAL_FACE_IDregex;releasedTentativeFacesnow only contains canonical UUIDs. Conservative semantics: non-canonical keys stay milestone'd to their person instead of being released under an invalid id.:0-style and junk keys being dropped while canonical outcome-A tentatives still release; existing release tests updated to canonical payload ids (Core's contract shape — the fixture face ids stay short, only payload rows carry UUIDs).KNOWN_ISSUES.md: ISSUE-165 (worker-fixed; the underlying data quirk —occurrence_keywith index suffix instate=tentative— recorded for a data-side cleanup).Test plan
PYTHONPATH=workers/people/src .venv/bin/python -m pytest workers/people/tests/ -q→ 363 passed, 1 skipped (pre-existing heif), 99 subtests — including the new filter regression and the updated release tests.semisupervised-v3).