Document Server state machine + clean up edge cases#202
Draft
Document Server state machine + clean up edge cases#202
Conversation
Contributor
Author
|
Marked as draft because I'm unsure on the cleanest solution for some cases, indicated with TODO's |
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
1 participant
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.
The existing logic didn't take into account the edge case that a connection can exist for a while in the server before being passed to the DHT itself (notably, during the handshake, and during the holepunching while the connection is still relayed).
I'm pretty sure this partially explains the Hyperswarm lifecycle issue documented here: https://github.com/holepunchto/hyperswarm/blob/d8eab5249ac76076a4257e2cdcad9d086f2c7d61/index.js#L291-L293