[snrc resolver] report expiry and availability correctly - #1861
Closed
brenzi wants to merge 10 commits into
Closed
Conversation
brenzi
changed the title
brenzi
force-pushed
the
ab/snrc-resolver-expiry-and-availability
branch
from
September 4, 2026 06:51
4b5c7bc to
e4e3d0d
Compare
brenzi
marked this pull request as ready for review
September 4, 2026 07:17
# Conflicts: # scripts/resolver/README.md # scripts/resolver/service/snrc-resolve.py # scripts/resolver/service/test_snrc_resolve.py
…piry-and-availability
…ry-and-availability
brenzi
removed this pull request from stack #1862
September 10, 2026 11:29
Collaborator
Author
|
superseded by #1863, which now carries this work against master |
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
2 participants
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.
Problem with #1860 alone: It prepares the resolver to be used to query availability of names without revealing them, but the response can be misleading because we don't handle expiry and reserved status meaningfully.
This PR fixes the problems above
Names.hs