fix(core): remove unused getTerminalOutput from BatchProcess#34604
fix(core): remove unused getTerminalOutput from BatchProcess#34604FrozenPandaz merged 2 commits intomasterfrom
Conversation
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 8fb55d9
☁️ Nx Cloud last updated this comment at |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Nx Cloud has identified a flaky task in your failed CI:
🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.
🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.
🎓 Learn more about Self-Healing CI on nx.dev
## Current Behavior `BatchProcess` accumulates all stdout/stderr output in `terminalOutputChunks` and exposes it via `getTerminalOutput()`, but nothing ever calls `getTerminalOutput()`. The accumulated strings are unique allocations (created via `chunk.toString()`), not shared with the output callbacks or `process.stdout.write`. For verbose batched tasks (e.g., Maven/Gradle with hundreds of tasks), this can hold tens to hundreds of MB for the entire batch duration. ## Expected Behavior Remove the dead accumulation code. stdout/stderr chunks are still forwarded to `process.stdout`/`process.stderr` and output callbacks as before — only the unused storage is removed. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> (cherry picked from commit 872b9c9)
## Current Behavior `BatchProcess` accumulates all stdout/stderr output in `terminalOutputChunks` and exposes it via `getTerminalOutput()`, but nothing ever calls `getTerminalOutput()`. The accumulated strings are unique allocations (created via `chunk.toString()`), not shared with the output callbacks or `process.stdout.write`. For verbose batched tasks (e.g., Maven/Gradle with hundreds of tasks), this can hold tens to hundreds of MB for the entire batch duration. ## Expected Behavior Remove the dead accumulation code. stdout/stderr chunks are still forwarded to `process.stdout`/`process.stderr` and output callbacks as before — only the unused storage is removed. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> (cherry picked from commit 872b9c9)
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
BatchProcessaccumulates all stdout/stderr output interminalOutputChunksand exposes it viagetTerminalOutput(), but nothing ever callsgetTerminalOutput(). The accumulated strings are unique allocations (created viachunk.toString()), not shared with the output callbacks orprocess.stdout.write.For verbose batched tasks (e.g., Maven/Gradle with hundreds of tasks), this can hold tens to hundreds of MB for the entire batch duration.
Expected Behavior
Remove the dead accumulation code. stdout/stderr chunks are still forwarded to
process.stdout/process.stderrand output callbacks as before — only the unused storage is removed.