Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash ToolArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What
When a shell command has to be force-killed via a fallback escalation (sending SIGKILL after a normal stop attempt fails), its result now carries a noExitStatus field marking that the reported exit code isn't a genuine one reported by the process, but an inferred stand-in.
Why
This lets anything reading the result tell apart a command that actually reported its own exit code from one that was forcibly terminated, avoiding misleading conclusions drawn from a fake exit status.
