Repository navigation
feat: add DHT provider and value maintenance - #346
Merged
Merged
Conversation
Republish locally provided keys before provider records expire and add configurable, bounded value-record expiry and garbage collection. Ensure maintenance workers share DHT shutdown and cover expiry and cancellation behavior with deterministic tests.
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.
Summary
Add configurable DHT maintenance with go-libp2p-compatible defaults: locally provided keys are republished every 22 hours, value records expire after 48 hours, and bounded value GC runs every 24 hours. Provider and GC workers stop through
stopDHTNode, and the public facade exposes configuration plus an injectable clock for deterministic tests.Value records are deliberately not auto-republished: as in go-libp2p core, the DHT cannot infer application ownership of arbitrary value keys, so applications must republish owned values before
dmcRecordMaxAge.Spec reference
Testing
cabal test all --test-show-details=direct— 1477 examples, 0 failuresCloses #292