Check HTTP status before parsing response body#673
Merged
miparnisari merged 1 commit intoauthzed:mainfrom Apr 20, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #673 +/- ##
==========================================
+ Coverage 43.19% 43.24% +0.04%
==========================================
Files 38 38
Lines 6035 6040 +5
==========================================
+ Hits 2607 2612 +5
Misses 3163 3163
Partials 265 265 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
miparnisari
approved these changes
Apr 17, 2026
6d777b5 to
fd35483
Compare
fd35483 to
bbebb7b
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
zed validatefetches a URL that returns a non-200 response (e.g. 404), the error page was fed to the schema parser, producing a confusing "invalid yaml" errorfailed to fetch ...: received HTTP 404Closes #671