-
Notifications
You must be signed in to change notification settings - Fork 248
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
[connection] update path challenge according to the draft [JF & CC] #189
Conversation
This looks like a good catch. Would you mind cleaning up the patch (removing commented code and debug statements)? |
Hello @ElNiak any chance of getting the code into a shape I can merge it? |
Hello, sorry we forget about that it will be done asap ! |
The PR seems to completely break the test suite would you mind updating it? |
@@ -1147,6 +1162,17 @@ def _find_network_path(self, addr: NetworkAddress) -> QuicNetworkPath: | |||
self._logger.debug("Network path %s discovered", network_path.addr) | |||
return network_path | |||
|
|||
def _find_network_challenge(self) -> QuicNetworkPathChallenge: | |||
# check existing network challenge | |||
for idx, network_chall in enumerate(self._network_challenges): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a complicated way of saying "always take the last challenge in the list"?
Hi @ElNiak do you plan to complete the work on this PR? |
Closing this in favor of the approach of [#483]. |
We try to modify the PATH_CHALLENGE part of the connection.py to follow this rule that we found with a testing tool Ivy. The problem before was that if the PATH_RESPONSE was received on a different path the challenge was considered as failed.
JF & CC