Tech-debt: pre-existing repo-wide ruff errors + non-hermetic systemd test #5

Closed
opened 2026-09-10 12:20:58 +00:00 by jmz · 1 comment
Owner

~11 pre-existing ruff check src errors in files the mesh milestones didn't touch (e.g. detectors/cert_expiry.py UP037, an S110 in engine.emit, RUF100s) — sweep in one pass.

Also tests/test_systemd_detector.py::test_no_run_capability_is_skipped fails on any host WITH systemd (shells to systemctl) — the one baseline failure throughout M1-M3. Make it hermetic (inject the runner) or skip when host systemd is present.

~11 pre-existing `ruff check src` errors in files the mesh milestones didn't touch (e.g. `detectors/cert_expiry.py` UP037, an `S110` in `engine.emit`, RUF100s) — sweep in one pass. Also `tests/test_systemd_detector.py::test_no_run_capability_is_skipped` fails on any host WITH systemd (shells to `systemctl`) — the one baseline failure throughout M1-M3. Make it hermetic (inject the runner) or skip when host systemd is present.
Author
Owner

Fixed in v0.18.0 (commit dadf719). Repo-wide ruff check src is now clean (S110 sites got real log lines or a justified noqa with rationale); the systemd baseline test is hermetic (injects the command runner) so the full suite is 0 failures.

Fixed in v0.18.0 (commit dadf719). Repo-wide `ruff check src` is now clean (S110 sites got real log lines or a justified noqa with rationale); the systemd baseline test is hermetic (injects the command runner) so the full suite is 0 failures.
jmz closed this issue 2026-09-10 16:17:44 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
public/warden#5
No description provided.