You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: stop guest state probes leaking cat errors into command output
Every code-vm invocation printed
cat: /run/sandbox/squid-allow.d/10-host-config.conf: No such file or directory
before the agent's own output. Session setup probes for the allowlist
fragment on each run, AdminOutput streams stderr to the caller, and that
fragment is legitimately absent whenever extraDomains is empty — which is
the default, so the message appeared every time.
Fixing only the reported line would have left four more probe reads with
the same defect, and this is already the second instance of it: the Squid
reconfigure fix silenced the write path and left the reads alone. So
reads go through Client.ReadFile, which discards stderr inside the guest
and passes the path as an argument rather than interpolating it into the
command string. No raw cat probes remain. Absence now returns empty
content, which is what every caller already treated a read failure as.
The suite asserts an agent command emits nothing of its own and that
hello yields exactly hello, so noise from a future probe fails a
test rather than reaching the terminal.
fakeRunner matches stubs on a substring of the argv instead of its exact
shape: keying on the shape had made these very tests pass empty content
silently when the read changed form.
0 commit comments