pgw#628: residency reporting v2 — content-addressed idempotent observations (0.52.0)#381
Merged
Merged
Conversation
…ations (0.52.0) Worker half of th#1070: every applied HelloAck opens a republish epoch; the reconcile pass re-announces verified cached identities (exact ref+digest) once per epoch even when unchanged — a re-received plan (redrive/overdue resend/reconnect) is the hub asking for a resync, and success observations are safe to emit late, twice, or across plan revisions under the v2 hub's digest acceptance. Job-path cache hits within an epoch stay deduped. gw#614 same-set no-cancel unchanged. Revert-turns-red test; mypy+ruff clean; full suite 649 passed/5 skipped. No forced fleet rebuild — v2 hubs accept 0.44-0.51 reports fine.
PaulFidika
marked this pull request as ready for review
July 24, 2026 03:59
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
1 participant
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.
Worker half of tensorhub th#1070 (hub v2 merged: tensorhub#624). Cherry-picked from chaos fa1a088 + uv.lock version re-resolve.
Every applied HelloAck opens a republish epoch: the reconcile pass re-announces verified cached identities (exact ref+digest ON_DISK/IN_RAM/IN_VRAM) once per epoch even when unchanged — a re-received plan (hub redrive, overdue resend, reconnect) is the hub asking for a resync, and success observations are safe to emit late, twice, or across plan revisions under the v2 hub's content-addressed acceptance. Job-path cache hits within one epoch stay deduped (no event spam). gw#614's no-cancel-on-same-set reconcile behavior is unchanged — under the v2 hub it is simply correct instead of a trap.
Tests: tests/test_residency_republish_pgw628.py over the real hub-double + blob host (revert-turns-red verified; one-per-epoch and no-spam asserted). mypy + ruff clean. Full suite on this head: 649 passed / 5 skipped.
Version floor note: NO forced fleet image rebuilds — v2 hubs accept 0.44–0.51 success reports unchanged; images pick up >=0.52.0 on their next routine rebuild for the lost-observation resync hardening.