Repository navigation
Fix captured response prefixes across multiple writes - #21
Open
bensynapse wants to merge 1 commit into
Open
bensynapse wants to merge 1 commit into
bensynapse wants to merge 1 commit into
Conversation
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.
I run Live Tennis API.
When response recording reaches its size limit, a later short write truncates bytes already saved. With a four byte cap, writes "abcd" and "e" capture "ae".
Capture now stops at the limit and keeps the original prefix. The complete response and byte count stay intact. This also fixes recorded ReadFrom calls.
The regressions cover chunk boundaries and the middleware's JSON log output. Eleven checks fail before the fix.
make test, make build and go vet ./... pass on Go 1.21.13 and 1.23.4. make coverage and make lint also pass on Go 1.23.4.