fix: return read error when ErrorResponse has nil Error field #1096
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.
This ensures the original read error is properly propagated when there's no actual API error to report.
Changes
stream_reader.go: Added nil check forrespErr.Errorbefore formatting error messageTestStreamReaderReturnsReadErrWhenErrorResponseHasNilErrorto verify the fixTesting
All existing tests pass, and the new test verifies that
io.EOFis properly returned instead of"error, <nil>".