jessey/rigdoctor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

fix(games): let the GUI Add-game dialog link a launcher & log folder #47

Merged
jessey merged 3 commits from feat/gpu-stress-and-drive-health into main 2026-05-29 15:00:00 +00:00
Conversation 0 Commits 3 Files Changed 13
+1077 -60
3 Commits
Author SHA1 Message Date
jesseyandClaude Opus 4.8 8f4824f576 chore(release): v0.43.0
tests / gui-smoke (pull_request) Successful in 31s
Details
tests / core (pull_request) Successful in 13s
Details 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 16:59:13 +02:00
jesseyandClaude Opus 4.8 edc2166011 feat(health): GPU stress monitor + per-drive SMART health/wear 
Two diagnostics for the load-correlated GPU crashes and for storage wear.

GPU stress (`rigdoctor stress` + a System Health "Stress test…" dialog): drive a GPU
load and sample sensors at high rate, then report per-metric min/avg/peak, time spent
above each temp threshold, power vs limit, throttling (decoded from the NVML
clocks-event bitmask), and any GPU fault (Xid / VA-space freeze / query-timeout hang)
in the window. Load source: explicit --command, an auto-detected loader, or
monitor-only (you launch the game). Analysis is a pure, unit-tested function.

Drive health (core/drives.py): parse full `smartctl --json` per drive into prioritized
findings — SMART verdict, derived life-left % (NVMe percentage_used or SATA
wear-leveling), power-on hours, TBW, temperature, and failure predictors
(reallocated/pending/offline sectors, NVMe media errors, low spare). Replaces the old
pass/fail-only check_smart; runs through the same elevated path (collect-priv / sudo),
degrading to "needs root" notes unprivileged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 16:59:06 +02:00
jesseyandClaude Opus 4.8 31ecf67ca7 fix(games): let the GUI Add-game dialog link a launcher & log folder 
The "Add game…" button only prompted for a name (single-field QInputDialog), so a
custom game couldn't be given its launch command or log dir from the GUI. Replace it
with a proper dialog: name + an optional launch command/script (with a file browser)
+ an optional log folder (auto-detected from the script's folder when left blank).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-29 16:58:56 +02:00