gstack's script runner and merge-queue checks now refuse cut-off command output (GST-3104) (#4502)

The helper that runs gstack's own scripts and `bash -c` commands, and
the merge queue's branch-ownership, stacked-test, release-version and
merge-group record checks, now fail with `SPAWN_OUTPUT_INCOMPLETE` when
Bun cuts a command's output off, instead of treating part of it as the
whole answer.

Why: #4492 added this for the scanners and gates but left these on
Node's `spawnSync`, and its release note claimed wider coverage than it
shipped.

Nothing to do: a new test stops any new gstack command from calling
Node's `spawnSync` directly.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
Garry Tanandcapy-ai[bot] authored and GitHub committed 2026-11-18 18:40:12 +00:00
1 parent d789dd965b
commit 2f57b07495
14 files changed
+237 -11

No files matched your search

+2 -1
View File
@@ -28,12 +28,13 @@
* Paths are forward-slashed: Bun's spawnSync on Windows returns ENOENT for a
* backslash exe path containing spaces, and bash reads backslashes as escapes.
*/
import { spawnSync, type SpawnSyncOptions, type SpawnSyncOptionsWithStringEncoding, type SpawnSyncReturns } from 'node:child_process';
import type { SpawnSyncOptions, SpawnSyncOptionsWithStringEncoding, SpawnSyncReturns } from 'node:child_process';
import * as fs from 'node:fs';
import * as path from 'node:path';
import { fileURLToPath } from 'node:url';
import { bunIsolationArgs } from './bun-isolation';
import { resultLine } from './result-codes';
import { spawnSync } from './spawn-sync';
export const BIN_DIR = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..', 'bin');