physnet: actually connect to manager #112
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
TheButlah
force-pushed
the
thebutlah/demo-do-connect
branch
from
803b760 to
c586aae
Compare
TheButlah
force-pushed
the
thebutlah/demo-do-connect
branch
from
c586aae to
34e8985
Compare
|
Forcing merge due to lack of review. |
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.
I've updated the code to properly spawn a future that will start the tokio runtime and perform the necessary steps to connect to the replicate manager.
Next step will be to use the newly connected manager resource to spawn an instance. The video showcases the UI flows and how connecting to a server that doesn't exist fails, but connecting to the one I start from the command line with a valid url succeeds.
Rebased on #111
output.mp4