Repository navigation
Save recoverable blocklists and handle DNS and iprange edge cases - #11
Merged
Merged
Conversation
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.
Save the domain, IPv4, and IPv6 text lists in per-run recovery checkpoints before the main processing stages. Preserve records from already parsed sources on a fatal input error. Each checkpoint can be reused as a feed.
Use forward DNS only. Skip local and reverse DNS names, and ignore answers in local address ranges. Existing input and allowlist rules still apply to explicit feed records.
If iprange fails or its output changes coverage, warn with the reason and use exact Python CIDRs for the affected family. Reproduced IPv6 reduction exit status 1 with iprange 2.1.1 and verified the bundle still completes.
All 37 unit tests passed, including recovery after source, DNS, and optimizer failures.