Repository navigation
fix: report network errors for gh: specs instead of a traceback - #430
Merged
Merged
Conversation
Only HTTPError was caught. A DNS or connection failure raises URLError and printed a full traceback. Assisted-by: ClaudeCode:claude-fable-5-1 ClaudeCode:claude-fable-5-1
henryiii
force-pushed
the
fix/gh-url-error
branch
from
October 7, 2026 15:48
97d7a87 to
a5e0dce
Compare
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.
🤖 AI text below 🤖
Only
HTTPErrorwas caught when building aGHPath. A DNS or connection failure raisesURLErrorand printed a full traceback. It is now reported the same way with exit code 1.Stacked on #429 (Windows fix) because both touch the same function and test file.