Skip to content

Conversation

@wchargin
Copy link
Contributor

Summary:
We’ve deployed production servers that support the handshake protocol
specified in #2878 and implemented on the client in #2879. This commit
enables that protocol by default.

Test Plan:
Running bazel run //tensorboard -- dev list still properly connects
and prints valid URLs. Re-running with the TensorBoard version patched
to 2.0.0a0 (in version/version.py) properly causes a handshake
failure. Setting --origin to point to a non-prod frontend properly
connects to the appropriate backend. Setting --api_endpoint to point
to a non-prod backend connects directly, skipping the handshake, and
printing https://tensorboard.dev URLs. Specifying both --origin and
--api_endpoint performs the handshake and overrides the backend
server only, printing URLs corresponding to the listed frontend.

Running git grep api.tensorboard.dev no longer finds any code results.

As a double check, building the Pip package and running it in a new
virtualenv still has a working tensorboard dev upload flow.

wchargin-branch: uploader-handshake

Summary:
We’ve deployed production servers that support the handshake protocol
specified in #2878 and implemented on the client in #2879. This commit
enables that protocol by default.

Test Plan:
Running `bazel run //tensorboard -- dev list` still properly connects
and prints valid URLs. Re-running with the TensorBoard version patched
to `2.0.0a0` (in `version/version.py`) properly causes a handshake
failure. Setting `--origin` to point to a non-prod frontend properly
connects to the appropriate backend. Setting `--api_endpoint` to point
to a non-prod backend connects directly, skipping the handshake, and
printing `https://tensorboard.dev` URLs. Specifying both `--origin` and
`--api_endpoint` performs the handshake and overrides the backend
server only, printing URLs corresponding to the listed frontend.

Running `git grep api.tensorboard.dev` no longer finds any code results.

As a double check, building the Pip package and running it in a new
virtualenv still has a working `tensorboard dev upload` flow.

wchargin-branch: uploader-handshake
@wchargin wchargin merged commit 846cd96 into master Nov 22, 2019
@wchargin wchargin deleted the wchargin-uploader-handshake branch November 22, 2019 02:17
wchargin added a commit to wchargin/tensorboard that referenced this pull request Nov 25, 2019
Summary:
We’ve deployed production servers that support the handshake protocol
specified in tensorflow#2878 and implemented on the client in tensorflow#2879. This commit
enables that protocol by default.

Test Plan:
Running `bazel run //tensorboard -- dev list` still properly connects
and prints valid URLs. Re-running with the TensorBoard version patched
to `2.0.0a0` (in `version/version.py`) properly causes a handshake
failure. Setting `--origin` to point to a non-prod frontend properly
connects to the appropriate backend. Setting `--api_endpoint` to point
to a non-prod backend connects directly, skipping the handshake, and
printing `https://tensorboard.dev` URLs. Specifying both `--origin` and
`--api_endpoint` performs the handshake and overrides the backend
server only, printing URLs corresponding to the listed frontend.

Running `git grep api.tensorboard.dev` no longer finds any code results.

As a double check, building the Pip package and running it in a new
virtualenv still has a working `tensorboard dev upload` flow.

wchargin-branch: uploader-handshake
@wchargin wchargin mentioned this pull request Nov 25, 2019
wchargin added a commit that referenced this pull request Nov 25, 2019
Summary:
We’ve deployed production servers that support the handshake protocol
specified in #2878 and implemented on the client in #2879. This commit
enables that protocol by default.

Test Plan:
Running `bazel run //tensorboard -- dev list` still properly connects
and prints valid URLs. Re-running with the TensorBoard version patched
to `2.0.0a0` (in `version/version.py`) properly causes a handshake
failure. Setting `--origin` to point to a non-prod frontend properly
connects to the appropriate backend. Setting `--api_endpoint` to point
to a non-prod backend connects directly, skipping the handshake, and
printing `https://tensorboard.dev` URLs. Specifying both `--origin` and
`--api_endpoint` performs the handshake and overrides the backend
server only, printing URLs corresponding to the listed frontend.

Running `git grep api.tensorboard.dev` no longer finds any code results.

As a double check, building the Pip package and running it in a new
virtualenv still has a working `tensorboard dev upload` flow.

wchargin-branch: uploader-handshake
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants