Skip to content

Conversation

@wchargin
Copy link
Contributor

Summary:
When TensorBoard launches its server, it prints a message to stderr
listing the URL on which it serves. This is convenient for humans, but
not for scripts: scripts would have to capture stderr and parse out the
appropriate line. As of this commit, TensorBoard will also write this
URL unadorned to a file given by --url_file.

Test Plan:
After building with bazel build //tensorboard, invoking TensorBoard
from ./bazel-bin/tensorboard/tensorboard with --help prints the new
argument with its help text (though the nice newlines are removed,
sadly).

Launching with --logdir x --url_file y --port 0 writes a URL to ./y
and concurrently launches the server; curl "$(cat y)" works.

Running bazel run //tensorboard -- --logdir x --url_file y does not
output to the right file, because bazel invokes tensorboard under a
different directory. But using --url_file /tmp/y still works even
under bazel run.

wchargin-branch: url-file

Summary:
When TensorBoard launches its server, it prints a message to stderr
listing the URL on which it serves. This is convenient for humans, but
not for scripts: scripts would have to capture stderr and parse out the
appropriate line. As of this commit, TensorBoard will also write this
URL unadorned to a file given by `--url_file`.

Test Plan:
After building with `bazel build //tensorboard`, invoking TensorBoard
from `./bazel-bin/tensorboard/tensorboard` with `--help` prints the new
argument with its help text (though the nice newlines are removed,
sadly).

Launching with `--logdir x --url_file y --port 0` writes a URL to `./y`
and concurrently launches the server; `curl "$(cat y)"` works.

Running `bazel run //tensorboard -- --logdir x --url_file y` does _not_
output to the write file, because `bazel` invokes `tensorboard` under a
different directory. But using `--url_file /tmp/y` still works even
under `bazel run`.

wchargin-branch: url-file
@wchargin wchargin requested a review from nfelt January 25, 2019 00:59
Copy link
Contributor

@nfelt nfelt left a comment

Choose a reason for hiding this comment

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

LGTM, but maybe let's wait to merge this until we know we will want to use it in this form?

@wchargin
Copy link
Contributor Author

Sure.

@wchargin
Copy link
Contributor Author

wchargin commented Feb 5, 2019

Closing in favor of #1806.

@wchargin wchargin closed this Feb 5, 2019
@wchargin wchargin deleted the wchargin-url-file branch February 5, 2019 01:46
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