20260925 - Tell retina-telemetry which tracker release it is carrying - #45
Merged
Merged
Conversation
Node ingest 1.6.0 lets a detection frame carry the node tracker's confirmed tracks, and adds versions.retina_tracker to the heartbeat so the server knows which release produced them. retina-telemetry reads that from RETINA_TRACKER_V, the way it already reads BLAH2_V for blah2, but nothing passed it in, so the field would have gone out empty on every node. It is the same variable, with the same default, that pins retina-tracker's image a few lines up. Reading the tag that selected the image is the only source of the version that needs no docker socket, which retina-telemetry deliberately does not have. Nothing changes on a node until retina-telemetry is released with 1.6.1 support: an unknown environment variable is ignored by the current image. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Node ingest 1.6.0 adds
versions.retina_trackerto the heartbeat, so the server knows which tracker release produced the tracks a node sends. retina-telemetry reads it fromRETINA_TRACKER_V, the way it readsBLAH2_V, but nothing passed it in.This passes the same variable, with the same default, that already pins retina-tracker's image. The image tag is the only source of the version that needs no docker socket, which retina-telemetry deliberately does not have.
Safe on its own. The current retina-telemetry image ignores the variable, so nothing changes on a node until a telemetry release reads it.
One follow-up. Once offworldlabs/retina-tracker#36 is released, the
v0.3.0default here (in both places) should move to the new tag. That is what makes tracks flow fleet-wide.Verified on jonathan-node-1 on 2026-09-25 as part of the telemetry live run: heartbeats to production carried
versions.retina_tracker.🤖 Generated with Claude Code