fix(skywire-cli): default uptime queries to v3 to match the CXO mirror - #4075
Merged
Conversation
0pcom
force-pushed
the
fix/cliuptime-default-v3
branch
from
August 22, 2026 14:16
c564e4b to
85548f2
Compare
The shared cliuptime table command defaulted --v to v2, but the deployment only mirrors the v3&days=30 /uptimes response over CXO. So `ut sd/mdisc/tpd` always CXO-missed and fell back to live dmsg, producing transient 'dmsg 202' errors. Default to v3 so queries hit the CXO cache. v1/v2 stay selectable via --v for the older response shapes. (There is no standalone uptime-tracker service anymore; uptime is per-service/TPD-integrated, and v3 is what those endpoints publish.)
0pcom
force-pushed
the
fix/cliuptime-default-v3
branch
from
August 22, 2026 14:55
85548f2 to
9c5c7b9
Compare
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.
Problem
The shared
cliuptimetable command (skywire cli ut {sd,mdisc,tpd}) defaulted--vto v2, but the deployment only mirrors the v3&days=30/uptimesresponse over CXO. So every defaultutquery CXO-missed and fell back to live dmsg, producing transientdmsg 202errors and unnecessary load.Note: there is no standalone uptime-tracker service anymore — uptime is per-service / TPD-integrated, and v3 is the shape those endpoints publish and mirror.
Fix
Default
--vtov3in the shared table command (covers sd/mdisc/tpd since they all use the same factory).v1/v2remain selectable via--vfor the older response shapes; the v3 payload still carries thedailypercentages the table renders. Help text and the tpdLong/header comments updated.Validation
go build ./cmd/skywire-cli/clean.skywire cli ut tpd --statsnow issues/uptimes?v=v3and returns data (1014 visors in a live run); with a running visor this hits the CXO cache instead of live dmsg.Backward-compatible:
--v v1/--v v2still work.