Nixpkgs version

• Unstable (26.11)

Describe the bug

When building a pnpm 11 package's pnpmDeps attribute, the log is spammed with:

qui-web-pnpm-deps> (node:7511) Warning: File descriptor 46 opened in unmanaged mode twice
qui-web-pnpm-deps> (node:7511) Warning: File descriptor 46 closed but not opened in unmanaged mode
qui-web-pnpm-deps> (node:7511) Warning: File descriptor 46 opened in unmanaged mode twice
qui-web-pnpm-deps> (node:7511) Warning: File descriptor 46 closed but not opened in unmanaged mode

When building multiple pnpm 11 packages on an aarch64-darwin GHA runner, after the same log messages the build will fail with:

2026-05-29T09:59:09.4366700Z qui-web-pnpm-deps> /nix/store/0y3vzjqz42dmyasywgr6ipcfb0nwdzvy-stdenv-darwin/setup: line 1831:  7511 Killed: 9                  pnpm install --force --ignore-scripts --registry="$NIX_NPM_REGISTRY" --frozen-lockfile

Steps to reproduce

This should give you the problematic logs on an aarch64-darwin machine:

nix build github:NixOS/nixpkgs/64c08a7ca051951c8eae34e3e3cb1e202fe36786#autobrr.passthru.autobrr-web.pnpmDeps --rebuild

Reviewing pnpm 11 PRs with nixpkgs-review-gha will emit the aforementioned logs and likely fail, previous instances:

• qui: update pnpmDeps' fetcherVersion from 3 to 4 #524812 (comment)
• fetchPnpmDeps: fix reproducibility of pnpm v11 store index #522703 (comment)

Expected behaviour

No log spam, no SIGKILL

Screenshots

No response

Relevant log output

Partial logs shown above.
Full logs for a failed GHA runner build: https://github.com/hesiod/nixpkgs-review-gha/actions/runs/26630712578/job/78478560785

Additional context

No response

System metadata

N/A

Notify maintainers

@Scrumplex @gepbird

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.
• I assert that I have read the automation/AI policy and that this issue report complies with it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.