Skip to content

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 1 commit into from
Oct 2, 2017
Merged

Make EPIPE tracebacks go away #595

merged 1 commit into from
Oct 2, 2017

Conversation

jart
Copy link
Contributor

@jart jart commented 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.

@jart jart requested a review from chihuahua September 30, 2017 01:52
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
Copy link
Contributor Author

jart commented Oct 2, 2017

@caisq There seems to be some kind of unrelated build break in the grpc debugger code.

  File "/home/travis/.bazel-output-base/bazel-sandbox/5608568710092001172/execroot/org_tensorflow_tensorboard/bazel-out/local-fastbuild/bin/tensorboard/backend/application_test.runfiles/org_tensorflow_tensorboard/tensorboard/backend/application_test.py", line 34, in <module>
    from tensorboard import main as tensorboard
  File "/home/travis/.bazel-output-base/bazel-sandbox/5608568710092001172/execroot/org_tensorflow_tensorboard/bazel-out/local-fastbuild/bin/tensorboard/backend/application_test.runfiles/org_tensorflow_tensorboard/tensorboard/main.py", line 38, in <module>
    from tensorboard.plugins.debugger import debugger_plugin as debugger_plugin_lib
  File "/home/travis/.bazel-output-base/bazel-sandbox/5608568710092001172/execroot/org_tensorflow_tensorboard/bazel-out/local-fastbuild/bin/tensorboard/backend/application_test.runfiles/org_tensorflow_tensorboard/tensorboard/plugins/debugger/debugger_plugin.py", line 35, in <module>
    from tensorboard.plugins.debugger import debugger_server_lib
  File "/home/travis/.bazel-output-base/bazel-sandbox/5608568710092001172/execroot/org_tensorflow_tensorboard/bazel-out/local-fastbuild/bin/tensorboard/backend/application_test.runfiles/org_tensorflow_tensorboard/tensorboard/plugins/debugger/debugger_server_lib.py", line 33, in <module>
    from tensorflow.python.debug.lib import grpc_debug_server
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/python/debug/lib/grpc_debug_server.py", line 30, in <module>
    from tensorflow.core.debug import debug_service_pb2
  File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/tensorflow/core/debug/debug_service_pb2.py", line 194, in <module>
    _sym_db.RegisterServiceDescriptor(_EVENTLISTENER)
AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'

@jart jart merged commit b58a82d into tensorflow:master Oct 2, 2017
@jart jart deleted the no-pipe branch October 2, 2017 23:54
@wchargin
Copy link
Contributor

wchargin commented Oct 3, 2017

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants