-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix concurrency issue with NodePeer update #8851
Merged
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
…e a guess client at a gateway, just ignore it and move on to another one Co-authored-by: Shubham Gupta <[email protected]>
…tus` for `sy.domains`
… networks for `sy.gateways`
- improve repr for domain and network registry to show online domains and networks
- `sy.gateways` and `sy.domains` work with python webserver nodes
- add a wait in `gateway_local_test` before checking for online domains Co-authored-by: Shubham Gupta <[email protected]>
- add some wait times before checking node connection status
…us.value` for `NodePeer` repr
…_delete_route_on_peer`
…ore checking for peer connection status
…default - update k8s integration tests accordingly - move skip test to the test file rather than in `tox.ini`
updates ping status related fields (in backgroudn threads) instead of the whole peer object to avoid outdated node routes (and possibly also other fields) issues
khoaguin
changed the title
[WIP] Fix concurrency issue with NodePeer update
Fix concurrency issue with NodePeer update
May 23, 2024
shubham3121
commented
May 27, 2024
shubham3121
commented
May 27, 2024
…when using `NetworkStash.update` in the network service
khoaguin
force-pushed
the
node-peer-partial-update
branch
from
May 28, 2024 13:08
5387757
to
cd44055
Compare
- in node peer update only update the fields that have changed
clean message during route exchange
- add serializable decorator to NodePeerUpdate
Nice work @khoaguin !!! 🎉 🔥 💯 |
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.
Description
sy.domains
.ParitialSyftObject
forupdate