-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panics when log is called after pty closes with EIO #53
Comments
This is really ugly, but I have a minimalistic repro case:
|
Allen-Webb
changed the title
panics for io
panics when log is called after pty closes with EIO
Dec 7, 2022
Allen-Webb
added a commit
to Allen-Webb/stderrlog-rs
that referenced
this issue
Dec 8, 2022
This makes sure stderrlog is well behaved after a pty closes. cardoe#53
Allen-Webb
added a commit
to Allen-Webb/stderrlog-rs
that referenced
this issue
Dec 8, 2022
cardoe
pushed a commit
to Allen-Webb/stderrlog-rs
that referenced
this issue
Jan 31, 2024
This makes sure stderrlog is well behaved after a pty closes. cardoe#53
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running into the following error:
failed to set color: Os { code: 5, kind: Uncategorized, message: "Input/output error" }', <registry path>/stderrlog-0.5.3/src/lib.rs:333:18
When I look at lib.rs, it looks inconsistent in that we ignore errors for
write!()
but panic on error for.set_color()
. I don't believe panicking in this scenario makes sense. I am working on getting a repro example.The text was updated successfully, but these errors were encountered: