Repository navigation
The net service reports tunnel paths to the cloud - #134
Merged
Merged
Conversation
This file contains hidden or 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
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.
Follows anyplaynet/cloud#107 (
POST /v1/tunnels/path, counted only).Cloud::tunnel_path(direct, upgraded)and the path constantTUNNEL_PATHin the API crate.anyplay::pathlog line), withupgradedwhen it moved from a relay to a direct path. Fire and forget: no wait, no retry, no message on failure; a cloud without the route (404) is not told and nobody notices.spec/cloud-api.md, plus the limit row;docs/DESIGN.mdupdated.{kind, upgraded}only; a cloud without the route answers an error that the service ignores.Need help on this PR? Tag
@codesmith-botwith what you need.