-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Make EPIPE tracebacks go away #595
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chihuahua
approved these changes
Sep 30, 2017
These errors aren't very helpful and they tend to fill up logs. They could be caused by something as innocent as `curl -N http://localhost:6006/ | head`. It could also be caused by firewalls, or perhaps the browser abruptly navigating somewhere else. So we wouldn't want users to mistake these as meaningful when troubleshooting.
@caisq There seems to be some kind of unrelated build break in the grpc debugger code.
|
Thank you! <3 |
jart
added a commit
to jart/tensorboard
that referenced
this pull request
Oct 3, 2017
These errors aren't very helpful and they tend to fill up logs. They could be caused by something as innocent as `curl -N http://localhost:6006/ | head`. It could also be caused by firewalls, or perhaps the browser abruptly navigating somewhere else. So we wouldn't want users to mistake these as meaningful when troubleshooting.
jart
added a commit
that referenced
this pull request
Oct 3, 2017
These errors aren't very helpful and they tend to fill up logs. They could be caused by something as innocent as `curl -N http://localhost:6006/ | head`. It could also be caused by firewalls, or perhaps the browser abruptly navigating somewhere else. So we wouldn't want users to mistake these as meaningful when troubleshooting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These errors aren't very helpful and they tend to fill up logs. They could be
caused by something as innocent as
curl -N http://localhost:6006/ | head
. Itcould also be caused by firewalls, or perhaps the browser abruptly navigating
somewhere else. So we wouldn't want users to mistake these as meaningful when
troubleshooting.