Fix panic when fetching resources fails due to network error #1506
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
Fixes a panic that occurs when fetching repository resource content fails due to a network error (e.g., connection timeout, DNS failure).
Problem
In
RepositoryResourceContentsHandler, the code calleddefer resp.Body.Close()before checking ifGetRawContentreturned an error:When a network error occurs,
respisnil, causing a panic when the deferred function tries to accessresp.Body.Solution
Move the error check before the defer statement:
Testing
Added
Test_repositoryResourceContentsHandler_NetworkErrorwhich uses a customerrorTransportthat always returns an error. This test ensures the handler gracefully handles network errors without panicking.Checklist
script/lintpassesscript/testpasses