-
Notifications
You must be signed in to change notification settings - Fork 418
Correct docs and marginally expand OMNameResolver
#3900
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
40e9174
Correct docs on `OMNameResolver::new_best_block`
TheBlueMatt 28fd617
Add a method to expire specific resolutions from `OMNameResolver`
TheBlueMatt 072675b
Allow use of `OMNameResolver` without validating DNSSEC expiry
TheBlueMatt 1855184
If we're built with `std`, always use real time to validate DNSSEC
TheBlueMatt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Given over how many hoops we're jumping in different places, I increasingly think we should lean on a standardized
TimeProvider
trait across LDK. This would allow us provide a very simple flow without introducing more assumptions/complications for 99% of users that can use thetime
feature. And anybody on WASM/no-std could plug-in their own time source.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.
It would be nice if Rust WASM weren't a trainwreck...In this case, though we aren't just using it for time, but its really rather a timer-tick to give us CPU time to expire old offers. A TimeProvider trait could clean up some of the time logic internally, but it wouldn't materially change the public API.