Skip to content

(v0.3.2) Dashboard fixes

Choose a tag to compare

@mitulgarg mitulgarg released this 02 May 08:30
· 10 commits to main since this release

Bug Fixes

env-doctor check --json exit codes corrected
Previously, having torch/tensorflow/jax uninstalled caused check --json to exit with code 1, making remote remediation commands appear as "failed" on the dashboard
even when the environment check ran cleanly. Exit codes now reflect actual problems:

┌──────┬─────────────────────────────────────────────────────────┐
│ Code │ Meaning │
├──────┼─────────────────────────────────────────────────────────┤
│ 0 │ All detected components are compatible │
├──────┼─────────────────────────────────────────────────────────┤
│ 1 │ Installed components have warnings or version conflicts │
├──────┼─────────────────────────────────────────────────────────┤
│ 2 │ One or more components in error state │
└──────┴─────────────────────────────────────────────────────────┘

Uninstalled libraries are informational — they no longer affect the exit code.

Improvements

Dashboard auto-refresh after remote command
After a queued command finishes executing on a machine, the Machine Detail page now automatically re-fetches and re-renders the diagnostics panel. No manual page
refresh needed to see updated GPU/driver/CUDA status post-remediation.

Full Changelog

v0.3.1...v0.3.2