)]}'
{
  "commit": "291a31ccece33debb3fde3d832aa5ed26cb14940",
  "tree": "c67e1991f1ef1b659dde8106de3afd53e0790bab",
  "parents": [
    "b26c8ef0535b2de24a0af4048370caf449eebabd",
    "d9ac1a5bc7c9eb680130a0d47efe9d5a1e3049d0"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Sat Jul 18 16:00:00 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sat Jul 18 16:00:00 2026 +0200"
  },
  "message": "Rollup merge of #159425 - Joel-Wwalker:157049-nul-error-context, r\u003dDarksonn\n\nWindows: add context when opening NUL for child stdio fails\n\nOpening `\\\\.\\NUL` for `Stdio::Null` can fail in some environments, and `Command::spawn`/`output()` passes the raw OS error through. In the reported case that was `NotFound`, which looks exactly like the program itself being missing. Add context saying what failed to open and for which stream:\n\n```\nfailed to open NUL device for child stdin: The system cannot find the file specified. (os error 2)\n```\n\nThe `ErrorKind` is kept. `raw_os_error()` on this path becomes `None` since the payload is now a message string. I don\u0027t see a way to make opening NUL fail in CI, so no test; verified by hand in a local build by pointing the open at a bogus device name and checking the error out of `Command::output()`.\n\nFixes rust-lang/rust#157049\n",
  "tree_diff": []
}