-
-
Notifications
You must be signed in to change notification settings - Fork 606
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Render local process infrastructure errors more verbosely. (#10368)
### Problem Currently we do not render a representation of the process when a process fails to start. ### Solution When processes fail due to infrastructure or implementation errors (ie, they fail to start at all, or we fail to receive output from them or capture their outputs), we should render the relevant process information directly in the error. This should be a relatively rare case. We do this only for the local process runner, because in the case of remote execution, infrastruture errors are much more common, and should potentially have a different treatment. ### Result In a sandbox without `echo` defined: ``` Failed to execute: Process { argv: [ "echo", "-n", "foo", ], env: {}, <snip> } Error launching process: Os { code: 2, kind: NotFound, message: "No such file or directory" } ```
- Loading branch information
Showing
3 changed files
with
33 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters