Skip to content

APP-16486 - viam server running version in app's agent_subsystem_versions should be accurate#244

Merged
cheukt merged 1 commit into
viamrobotics:mainfrom
cheukt:only-bump-viam-server-running-if-stop-succeeds
May 28, 2026
Merged

APP-16486 - viam server running version in app's agent_subsystem_versions should be accurate#244
cheukt merged 1 commit into
viamrobotics:mainfrom
cheukt:only-bump-viam-server-running-if-stop-succeeds

Conversation

@cheukt
Copy link
Copy Markdown
Member

@cheukt cheukt commented May 26, 2026

technically the ViamServerRunningVersion is a reflection of the desired running version (since it will be populated even if the viam-server has not successfully started up), but this change is better than what it is now.

maybe we should push the viam-server state too (running, initializing, etc)

@cheukt cheukt requested a review from EvanDorsky May 26, 2026 22:11
@cheukt cheukt added the dev-release Build and publish agent binaries with a dev version label May 26, 2026
@cheukt cheukt requested review from benjirewis and removed request for EvanDorsky May 28, 2026 15:47
Copy link
Copy Markdown
Member

@benjirewis benjirewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

More broadly though: what's the point of viam-agent and viam-server both submitting a viam-server version? Is another possible solution to stop reporting viam-server versions from viam-agent? Especially if the values aren't used anywhere in the frontend and the viam-server versions reported by agent aren't as accurate as the one reported by viam-server itself.

@benjirewis
Copy link
Copy Markdown
Member

maybe we should push the viam-server state too (running, initializing, etc)

Similar question there for me: why can't we just rely on the frontend querying viam-server directly for its status?

@cheukt
Copy link
Copy Markdown
Member Author

cheukt commented May 28, 2026

More broadly though: what's the point of viam-agent and viam-server both submitting a viam-server version? Is another possible solution to stop reporting viam-server versions from viam-agent? Especially if the values aren't used anywhere in the frontend and the viam-server versions reported by agent aren't as accurate as the one reported by viam-server itself.

good point, i think from my perspective the view from agent is useful, and especially if agent is trying to run viam-server at a specific version but failing to (the viam_server version field in that map tracks the desired version, while viam_server_running tracks the version attempted at running).

Similar question there for me: why can't we just rely on the frontend querying viam-server directly for its status?

there's the case that viam-server is just not coming up at all where having some diagnostic from agent may be useful

@cheukt cheukt added dev-release Build and publish agent binaries with a dev version and removed dev-release Build and publish agent binaries with a dev version labels May 28, 2026
@cheukt cheukt merged commit 87871b1 into viamrobotics:main May 28, 2026
26 checks passed
@cheukt cheukt deleted the only-bump-viam-server-running-if-stop-succeeds branch May 28, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dev-release Build and publish agent binaries with a dev version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants