Fix nil pointer dereference in meta-data get on API timeout#3682
Merged
Conversation
When the API request times out or fails with a network error, the response is nil. Accessing resp.StatusCode without a nil check causes a panic. Amp-Thread-ID: https://ampcode.com/threads/T-019bfcda-b7d4-726d-a58e-1190729c8b6d
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
moskyb
approved these changes
Jan 27, 2026
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
2 participants
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.
When the meta-data get API request times out or fails with a network error, the response object is nil but err is non-nil. The code was accessing resp.StatusCode to check for a 404 without first verifying that resp wasn't nil, causing a panic.
This adds a nil check before accessing the response status code.