Skip to content

Catch only socket.error because other errors should be handled by application #57

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

Merged
merged 1 commit into from
Jul 20, 2016

Conversation

repeatedly
Copy link
Member

Refer: #55

@repeatedly repeatedly merged commit d3a89e1 into master Jul 20, 2016
@coveralls
Copy link

coveralls commented Jul 20, 2016

Coverage Status

Coverage remained the same at 94.964% when pulling 9d33cc3 on catch-only-socket-exception into c11315b on master.

@arcivanov arcivanov deleted the catch-only-socket-exception branch December 10, 2017 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants