fix(gradle): destroy streams on exit to prevent daemon pipe hang

[nimo71]

Current Behavior

execGradleAsync() in exec-gradle.ts can hang indefinitely during project graph creation. This manifests as Nx freezing on "Creating project graph nodes" — particularly in CI environments, but also reproducible locally.

Expected Behavior

execGradleAsync() should resolve/reject promptly after the Gradle task completes, regardless of whether the Gradle daemon continues running in the background.

Root Cause

execGradleAsync() uses execFile() with shell: true, which spawns a shell wrapper process. The Gradle daemon, started by gradlew, inherits the shell's stdout/stderr pipe file descriptors. After the nxProjectGraph task completes:

1. The gradlew wrapper script exits
2. The Gradle daemon continues running, holding the inherited pipe FDs open
3. The shell wrapper process cannot exit because its child (the daemon) still holds its pipes
4. Node.js never fires the exit event on the child process
5. The Promise in execGradleAsync() never resolves

This is a well-documented interaction between:

• nodejs/node#5637 — execFile hangs when child exits but disowned children hold pipes
• gradle/gradle#3987 — Gradle daemon inherits parent file descriptors

Fix

Destroy stdout/stderr streams immediately after the exit event fires. By this point, all output data has already been buffered into the stdout variable via the data event handlers, so no output is lost. Destroying the streams releases the pipe FDs from Node's perspective, allowing the shell wrapper to exit and the Promise to resolve — regardless of daemon state.

cp.on('exit', (code, signal) => {
    if (code === null) code = signalToCode(signal);
    // Forcibly destroy streams to prevent Gradle daemon pipe hang.
    cp.stdout?.destroy();
    cp.stderr?.destroy();
    if (code === 0) {
        res(stdout);
    } else {
        rej(stdout);
    }
});

Workarounds Users Currently Need

Without this fix, users must resort to:

• org.gradle.daemon.idletimeout=5000 in gradle.properties (adds 5s latency per invocation)
• CI retry loops with timeout + pkill -f GradleDaemon (unreliable, wastes CI minutes)
• --no-daemon flag (doesn't work reliably with Gradle 8.1+/9.x — a "single-use daemon" is still forked when org.gradle.jvmargs is set)

Related Issues

• NX project graph calculation hanging indefinitely #29618 — NX project graph calculation hanging indefinitely
• CI Hanging at Creating project graph nodes with 7 plugins #32788 — CI hanging at "Creating project graph nodes"
• @nx/gradle is extremely slow when compared to running gradle directly #31835 — @nx/gradle extremely slow compared to running Gradle directly
• Nx operations hangs indefinitely #27494 — Nx operations hang indefinitely

[netlify]

✅ Deploy Preview for nx-docs canceled.

Name	Link
🔨 Latest commit	29adb96
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/69bc140b3fd0510008fcc3ae

[netlify]

✅ Deploy Preview for nx-dev canceled.

Name	Link
🔨 Latest commit	29adb96
🔍 Latest deploy log	https://app.netlify.com/projects/nx-dev/deploys/69bc140b091c9600080bda5a