Conversation
Saved command-mode ws.script entries are PTY-backed, so nextest and cargo redraw their progress bars into the captured buffer (one full-suite run produced ~530 KB of cursor-control sequences and overflowed an agent's context). Export NEXTEST_SHOW_PROGRESS=none and CARGO_TERM_PROGRESS_WHEN=never on the Rust gate targets, overridable from the environment or command line, and point the AGENTS.md gate guidance at the make targets. Agent-Id: agent-be1f9de1-55b4-4320-a704-77cd94a365ed
Contributor
Author
|
Companion intentd docs PR: intent-hq/intentd#1795 |
🤖 Augment PR SummarySummary: This PR suppresses interactive Cargo and nextest progress rendering for Make-based Rust gates run through PTY-backed saved scripts. Changes: It adds overrideable target-scoped environment defaults in the Makefile and documents the PTY output-buffer hazard and equivalent raw-command flags in 🤖 Was this summary useful? React with 👍 or 👎 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Agents run the Rust gates as saved command-mode
ws.scriptentries, which are PTY-backed. nextest and cargo therefore see an interactive stderr and redraw their progress bars into the captured buffer. One fullintent-acp+intent-servicesrun produced ~530 KB ofESC[10A / ESC[2K / ESC[1Bcursor-control sequences around a few useful lines; the hook wake built from that buffer overflowed an agent's context (413) and cost a re-delegation.make test-intentdalready pipes nextest's stdout throughscripts/resumable_nextest.py, so the noise is entirely on stderr (nextest progress bar + cargo build progress) — environment variables fix both without touching the Python wrapper.What
Makefile: target-specificexport NEXTEST_SHOW_PROGRESS ?= noneongate test test-intentd coverage-e2e coverage-allandexport CARGO_TERM_PROGRESS_WHEN ?= neveron those pluscheck clippy build-intentd.?=keeps env / command-line overrides working (make test NEXTEST_SHOW_PROGRESS=barrestores the bar for a human at a terminal).NEXTEST_HIDE_PROGRESS_BARis deprecated on the pinned nextest 0.9.143, henceNEXTEST_SHOW_PROGRESS.AGENTS.md(Resuming local Rust gates): compress the saved-script bullet to name the PTY hazard and the two flags, pointing at themaketargets.CI already sets
CI=true, under which both tools are non-interactive; CI output is unchanged.Companion docs PR on intentd: intent-hq/intentd — "docs(agents): lead the Gates section with make targets and the PTY progress-bar caveat" (link in the PR conversation once opened).
Verification
make -n gate test coverage-all checkparse;make -pshows the target-specific bindings;make -n test-intentd NEXTEST_SHOW_PROGRESS=barreports the command-line value winning.make test-intentdas a PTY-backed saved script: cursor-sequence count inws.script.outputis 0 (evidence in the workspace spec).make docs-checkpasses.