chore: graceful handling of SIGPIPE

[guipublic]

Description

Problem*

Resolves #8534

Summary*

handle SIGPIPE when printing to stdout

Additional Context

I tried 'execute', 'compile' and 'info', but some other println may need to be replaced.

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 7686ee0	Previous: c109ac7	Ratio
rollup-block-root	244 s	180 s	1.36

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[TomAFrench]

Wouldn't this require us to wrap every instance of println?

[guipublic]

Wouldn't this require us to wrap every instance of println?

Probably, compile with output is failing, I will try to fix it and see if is a lot of refactoring of not.

[TomAFrench]

If this is something which we're need to wrap all instances of println then I'd say it's probably not worth going forwards with this. It's going to be annoying to guarantee that we don't have any unwrapped printlns and we don't really unlock much with this anyway so it's probably not worth the maintenance burden.

[guipublic]

For 'nargo compile', it was just 3 println! to replace.
So far the impact is small and it's not critical if not exhaustif I believe.

[jfecher]

I wonder what cargo does internally for this. It doesn't seem to panic in the same way when I run e.g. cargo run | echo "${missing_cmd}"

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 98af63a	Previous: 42429ab	Ratio
test_report_AztecProtocol_aztec-packages_noir-projects_noir-protocol-circuits_crates_private-kernel-lib	2 s	1 s	2

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[jfecher]

Let's combine print_to_stdout and format_args in a macro for some brevity

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: f67a382	Previous: 80b04ec	Ratio
private-kernel-inner	0.018 s	0.014 s	1.29

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench