feat(kad): update republish interval and expiration time defaults#3230
Merged
Conversation
Applies changes from libp2p/specs#451 New defaults are: Record Expiration: 48h Record Republish Interval: 22h Closes #3229
thomaseizinger
approved these changes
Dec 13, 2022
Member
|
@thomaseizinger I added |
Contributor
I guess this is semantically breaking yeah. |
Member
|
@lidel friendly ping. Can you add a changelog entry? Let us know if you want us to take over. |
Contributor
|
My first contribution here (: Just added the changelog entry, let me know if anything else is required. |
Contributor
|
This pull request has merge conflicts. Could you please resolve them @lidel? 🙏 |
0b92650 to
1ef309e
Compare
Contributor
|
This pull request has merge conflicts. Could you please resolve them @lidel? 🙏 |
Rewording the the choices to clearly direct technical questions to GH dicussions and community discussion to discuss.libp2p.io. Pull-Request: #5116.
Pull-Request: #5239.
superseeds #5248, sorry @drHuangMHT only saw yours now, can you review this one? https://github.com/libp2p/rust-libp2p/actions/runs/8377129630/job/22938498078?pr=5253#step:6:843 is a bug, see [here](rust-lang/rust-clippy#12377) Thanks! Pull-Request: #5253.
In browsers, only the code 1000 and codes between 3000-4999 are allowed to be set by userland code: https://websockets.spec.whatwg.org/#dom-websocket-close I found this while debugging use-after-free errors in our WASM application. Turns out, when connections are timing out, libp2p in rust drops them, but does not seem to close them explicitly (we are using libp2p-swarm). This led to these WebSockets still emitting events, the handlers of which were already dropped on the rust side, though. A long investigation led me to have a look into the `Result` that gets returned from `close_with_code_and_reason`, and it turns out it's an error! Specifically: ``` InvalidAccessError: Failed to execute 'close' on 'WebSocket': The code must be either 1000, or between 3000 and 4999. 1001 is neither. ``` This PR only fixes the failing closing of the WebSocket, not the remaining use-after-free problem. Pull-Request: #5229.
## Description mergify automatic approval for dependabot PR's was disabled on #5208 following malfunctioning. This PR re-enables mergify's automatic merge of Dependabot PR's and the `trivial` label with the syntax [suggested on mergify's doc](https://docs.mergify.com/integrations/dependabot/#2-pr-approval)
Pull-Request: #5257.
Pull-Request: #5258.
Pull-Request: #5261.
Pull-Request: #5262.
Pull-Request: #5263.
Pull-Request: #5256.
Pull-Request: #5234.
Pull-Request: #5259.
Pull-Request: #5237.
Pull-Request: #5235.
Pull-Request: #5265.
Pull-Request: #5236.
Pull-Request: #5233.
Pull-Request: #5216.
jxs
approved these changes
Mar 29, 2024
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
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
This patch applies changes from libp2p/specs#451. In particular, the new defaults are:
Closes #3229.
Notes
Links to any relevant issues
Open Questions
Change checklist