Repository navigation
modeld: publish the Jetson's model sha256 beside the local receipt - #23
Merged
Merged
Conversation
… receipt While a Jetlink Jetson drives, modelIdentity only carried the local small model's receipt, so logs (and sites reading them) showed "small". modeld now also publishes a 'modeld.jetlink' logMessage (sha256, checkpoint, sinceMonoNs) every 5 s while the Jetson is active, and a cloudlog 'modeld.jetlink' event each time the active Jetson model changes. The local receipt, ModelVariant and logged_model_load are unchanged, so on-device status, UI and recovery read the same as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
trung791997
force-pushed
the
jetlink-model-identity
branch
from
November 11, 2026 18:10
924cc51 to
7895e8d
Compare
trung791997
changed the base branch from
night-star7-vasm-jetson
to
vasm-jetson-updater-bridge
November 11, 2026 18:10
Process replay diff reportReplays driving segments through this PR and compares the behavior to reviewed reference outputs. Show changes |
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.
What
While a Jetlink Jetson drives,
modelIdentitycarried only the local small model's receipt (modeld records SMALL on every Jetson handover), so the logs, and the Polaris site reading them, showed the drive as "small / unverified".modeld now also publishes, while the Jetson is active:
modelIdentitylogMessage every 5 s:{"msg": {"event": "modeld.jetlink", "version": 1, "active": true, "sha256": "<64 hex>", "checkpoint": "<str|null>", "sinceMonoNs": <int>}}modeld.jetlinkevent each time the active Jetson model changes, including going inactive (active: false, sha256: null).The local receipt,
ModelVariantandlogged_model_loadare unchanged, so on-device status, UI, recovery and galaxy drive analysis read the same as before. Galaxy ignores the new event, and a test checks it is never read as a load.Evidence
Static only, from unit tests; no drive yet.
starpilot/models/tests/test_receipt.py: 13/13 pass, including the new Jetson test (rate limit, one cloudlog per model, no marker while inactive, malformed sha rejected, failure reported without raising).starpilot/models/tests: 8 tests fail and 6 can't load, and the set is identical with and without this change. The ones that can't load hit the aarch64.sofiles.For the site
Polaris could treat time covered by an active
modeld.jetlinkas "big model (Jetson), sha256 = X" and check X against the registry.modelV2.bigis a cross-check.🤖 Generated with Claude Code