Skip to content
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

ignore error from set_read_timeout #3243

Merged
merged 1 commit into from
Feb 25, 2020

Conversation

antiochp
Copy link
Member

Resolves #3242.

We do not actually care about the error when 0 is passed in as a timeout.

We do care about this throwing weird errors if the connection is disconnected when we attempt to set the timeout.

@antiochp antiochp added this to the 3.1.0 milestone Feb 25, 2020
@antiochp antiochp added the bug label Feb 25, 2020
@antiochp antiochp force-pushed the set_read_timeout_error branch from 0e0ad61 to b95645e Compare February 25, 2020 19:28
Copy link
Contributor

@jaspervdm jaspervdm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can confirm that it no longer panics

20200225 20:53:07.996 DEBUG grin_p2p::conn - try_break: exit the loop: Connection(Custom { kind: UnexpectedEof, error: "failed to fill whole buffer" })
20200225 20:53:08.004 DEBUG grin_p2p::conn - Shutting down reader connection with ?

@antiochp antiochp merged commit 8a15007 into mimblewimble:master Feb 25, 2020
@antiochp antiochp deleted the set_read_timeout_error branch February 25, 2020 20:23
@antiochp antiochp mentioned this pull request Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

panic on set_read_timeout when wifi disabled
2 participants