Exclude malformed URLs from catalog build instead of crashing - #325
Merged
Conversation
…uild Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
source-archive catalogcrashed withValueError: Invalid IPv6 URLwhen a manifest contained an unparsable URL (e.g. a barehttp://[extracted from a bot comment), which killed the weekly catalog rebuild on 2026-07-13. This wraps theurlsplitcall sites in catalog.py so parse-raising URLs are routed to the existing "malformed" exclusion category instead of raising. Adds a regression test that a manifest record with such a URL builds cleanly and counts as excluded/malformed.🤖 Generated with Claude Code