You’re missing the problem that the text/pipe interface is likely the API bug that reliably creates this failed behavior across most (almost all?) implementations. Bad interfaces yield bad behaviors.
-
It’s not about piling on. There’s an old textpipe interface mode that doesn’t work very well, and there aren’t exactly resources to replace. The game is dispassionately understanding the engineering problems and not just blamestorming.
Okay, so what's the plan here? Convert it to a shared library, hope people pay attention to *those* return codes? Add a non-streaming command line option (and plead everyone uses it)? How is this better than just checking the damn exit code?
-
-
I'd understand if this were some subtle implication of the pipe interface, but we're literally talking about ignoring exit status here. This is security tool 101. Heck it's programming 101. Check your error codes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
*Clearly* the answer is to have GPG use /proc to find out which pid owns the other side of stdout and send a SIGKILL to it if something goes wrong.
-
That's both clever and radical, I've just learn something :)
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.