OCTADE

@octade@soc.octade.net

(Owner soc.octade.net) (5&2)()()

Director of the International Department of Civil Disobedience.

For thoughtful response to thoughtful inquiry contact my email. Don't send me private direct messages on the Fediverse. If you have a general question ask it in a public timeline. I block users who send me annoying private messages about things that should be asked in a public timeline.

I sometimes post links to items I find curious, interesting, or of research and study value. This does not necessarily mean that I agree with the linked matter. Don't assume.

NAME : Raze
ABOUT : https://soc.octade.net/octade/p/1738730010.732958
LINKS : https://soc.octade.net/octade/p/1738730079.782260
SITE : https://octade.net
NEWS : news://alt.flashback | news://alt.crossover

SLOGAN : Speak not with words. Speak with work product.

PRONOMS : | | | | | |





LINKS

Cryptography project site
Publications
ORCID
[Netnews] Find me on in alt.rhubarb.
Git Repositories
Keyoxide1
Keyoxide2
BlueSky
HackerNews
Internet Archive

0 ★ 0 ↺

[?]OCTADE » 🌐
@octade@soc.octade.net

> thread '

' panicked at 'failed printing to stdout: Broken pipe (os error 32)', library/std/src/io/stdio.rs:1015:9

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

This ought to be suppressed by default. The old GNU tools and coreutils I was using handled broken pipes gracefully by not bothering the user during commands that are meant to break a pipe as part of the stream processing. Now I have to re-write all my hundreds of scripts to trap this kind of stuff. Maybe they just want to make sure you know Rust is under the hood. IDK.

Programming has blown up into utter ridiculousness. I think I need to go touch grass again.

...

[?]Justin Fitzsimmons » 🌐
@smn@l3ib.org

@octade what causes pipes to break? and what techniques were the old tools using to gracefully handle it?

    ...

    History

    about this site - powered by snac/2.93-dev