-
Notifications
You must be signed in to change notification settings - Fork 108
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
Iterate the Message Protocol Between Agent <-> --subordinate #789
Comments
michaelquigley
added a commit
that referenced
this issue
Nov 8, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 8, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 12, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 12, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 12, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 12, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 13, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 13, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 13, 2024
michaelquigley
added a commit
that referenced
this issue
Nov 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current protocol does not cleanly support error handling in the handshake between the new zrok Agent and the
--subordinate
modezrok share
andzrok access
processes.Need to make the bootstrapper in the Agent more resilient to stray messages before the bootstrap message. Then move the bootstrap message down to the very end of the bootstrap protocol to properly support errors throughout the process.
The text was updated successfully, but these errors were encountered: