Skip to content

fix(dashboard): pin utf-8 on the handlers_system subprocess call - #27015

Merged
javenciu merged 1 commit into
mainfrom
fix/subprocess-encoding-dashboard-handlers-system
Nov 1, 2026
Merged

javenciu merged 1 commit into
mainfrom
fix/subprocess-encoding-dashboard-handlers-system

Conversation

@javenciu

@javenciu javenciu commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A text-mode subprocess call in 1 file decodes its child's output as UTF-8 on every platform instead of the locale's code page.

The subprocess-encoding gate counts, per file, the sites the repo still tolerates. This PR retires: 1 src/kiro_crew/dashboard/handlers_system.py.

Why it matters

Without an explicit encoding, subprocess.run(..., text=True) decodes with the locale code page, which on Windows is not UTF-8: non-ASCII output becomes mojibake or raises UnicodeDecodeError (#5249). The repo lists every such call per file in .github/subprocess-encoding-baseline.txt and the gate lets each count only shrink.

Not a goal

  • Calls in files not listed here (each is its own one-mechanism PR).
  • Changing what any child process does or how its output is used.
  • Any refactor or reformatting of untouched lines.

What changed (motivation → approach → change)

Each call below now passes encoding="utf-8" beside its text=True, and the file's baseline line is removed.

  • src/kiro_crew/dashboard/handlers_system.py:520: the check_output(...) call in _scan_mcp_processes
  • .github/subprocess-encoding-baseline.txt: removed 1 src/kiro_crew/dashboard/handlers_system.py.

Backwards compatibility

Compatible: the call's return type and the output's meaning are unchanged; only the decode encoding is pinned.
Removes nothing: a baseline entry is a tolerance the gate stops needing, not a capability.

Tests

  • Red: with the file put back to main and the baseline line still deleted, RATCHET_SCOPE_WHOLE_TREE=1 python3 scripts/check_subprocess_encoding.py exits 1: ::error file=src/kiro_crew/dashboard/handlers_system.py::text-mode subprocess call without encoding= (decodes with the ....
  • Green: with the edit, python3 scripts/check_subprocess_encoding.py --test && python3 scripts/check_subprocess_encoding.py exit 0.
  • test/test_resource_health_endpoint.py: 3 passed with the edit (imports kiro_crew.dashboard.handlers_system)
  • test/test_system_memory.py: 8 passed with the edit (imports kiro_crew.dashboard.handlers_system)
  • flake8 clean on the touched file; the repo's baselined black gate passes.
  • Proof: not provable -- other: the defect needs a non-UTF-8 locale code page; the encoding gate above is the check

Manual verification

N/A: the subprocess-encoding gate checks the changed call directly.

Sibling sweep

Swept: python3 scripts/check_subprocess_encoding.py, the gate's own scan of every text-mode subprocess call. The other files it reports keep their rows in .github/subprocess-encoding-baseline.txt; each is retired by its own PR.
Sibling: src/kiro_crew/dashboard/handlers_system.py:520 -- changed here

Pattern harvest

Rule candidate: none new; the rule is already enforced by scripts/check_subprocess_encoding.py (a baselined CI gate that flags every text-mode subprocess call without an explicit encoding), and this PR retires baseline entries under it.

Screenshots / video

Why no screenshot: nothing renders; this change pins a subprocess decode encoding and a CI baseline only.

No issue exists; burn-down of the subprocess-encoding gate baseline (precedents #20146, #20142, #20147).

Pin UTF-8 on the text-mode subprocess call(s) in src/kiro_crew/dashboard/handlers_system.py and drop the file's row
from .github/subprocess-encoding-baseline.txt, so the subprocess-encoding gate stops tolerating it.
@javenciu
javenciu requested review from a team and KiroCrewCaptain as code owners November 1, 2026 11:18
@javenciu
javenciu requested a review from cruisercohen November 1, 2026 11:18
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 1, 2026
@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 6611862872aa28555ff514f4d1f089e4c540590d touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 6611862872aa28555ff514f4d1f089e4c540590d — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: this pins the decode encoding of one ps read that runs only on hosts without /proc, and a broad except already wraps it.

Notes

  • A single process with non-UTF-8 bytes in its argv still raises inside the broad except, and every MCP count silently drops to 0. Adding errors="replace" would keep the counts, since the code only matches ASCII signatures. The failure is the same as before this PR, so it is not a regression.

[DESIGN-REVIEWED] 6611862

Description read

[DESCRIPTION-READ] 2140b37ddf02ad1a62f30ad9e2a9843f8ba1f52249917b4ea315763feb9853e8

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 6611862872aa28555ff514f4d1f089e4c540590d — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing to check.

What this change ships

Inventory (2 items) — 2 justified

Intent: shrink the subprocess-encoding baseline by pinning a decode encoding on one ps call in the dashboard's MCP-process scan. This is a FIX.

  1. The dashboard's MCP-process scan decodes ps output as UTF-8 whatever the locale is — justified
  2. The subprocess-encoding gate stops tolerating an unpinned call in handlers_system.py — justified

[FIRST-PRINCIPLES-REVIEWED] 6611862

Description read

[DESCRIPTION-READ] 9a080b88818edfb04f0f8214395eee0020511a4009b381adef25bf3af2206f28

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 6611862872aa28555ff514f4d1f089e4c540590d — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 6611862

Verdict parsed from the review's SHA-scoped output markers for commit 6611862872aa28555ff514f4d1f089e4c540590d.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 6611862872aa28555ff514f4d1f089e4c540590d false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 6611862872aa28555ff514f4d1f089e4c540590d and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 6611862

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 6611862872aa28555ff514f4d1f089e4c540590d false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 1, 2026
@javenciu
javenciu enabled auto-merge (squash) November 1, 2026 12:03

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Tier 1 auto-approve: fix (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, security checklist all-NO, no reviewer-lane findings, readiness signal fresh for this head SHA, declared category matches the diff. Category: bug fix: pins utf-8 on one ps subprocess call in the dashboard system handler and drops its encoding-baseline row.

@javenciu
javenciu merged commit 13529a1 into main Nov 1, 2026
95 checks passed
@javenciu
javenciu deleted the fix/subprocess-encoding-dashboard-handlers-system branch November 1, 2026 13:22
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants