This website requires JavaScript.
Explore
Help
Sign In
Mirrors
/
ProxMenux
Watch
1
Star
0
Fork
0
You've already forked ProxMenux
mirror of
https://github.com/MacRimi/ProxMenux.git
synced
2026-06-11 11:06:24 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
7a1fe0b0fcff8f5ab74dde29c57b47c7a2cc4ea3
ProxMenux
/
AppImage
/
ProxMenux-Monitor.AppImage.sha256
2 lines
65 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Persist resolution_reason on resolve_error so the audit log is useful The UPDATE in `_resolve_error_impl` only touched `resolved_at` — the `reason` argument every caller passes was silently dropped, and the `resolution_reason` / `resolution_type` columns stayed NULL for every auto-resolved error. The columns were added back in a previous sprint for exactly this audit-log purpose, but the writer was never updated to populate them. Fix the SQL to write `resolution_reason = ?` and tag `resolution_type = COALESCE(existing, 'auto')` so admin-cleared errors (whose type is set elsewhere) keep their value while the default auto path correctly labels itself. Verified end-to-end on the lab host: re-injected the `disk_nvme2n1` warning, waited one scan cycle, the row now reads `resolution_type='auto'` and `resolution_reason='Transient I/O cleared, SMART now reports healthy'` — previously these columns stayed NULL even though the resolve_error call passed a descriptive reason. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-01 23:02:52 +02:00
6f083dbae1558612f5036a0a10a9ded23024ae86dfd7914393f7e3d5d11ae853
Reference in New Issue
Copy Permalink