Use copied fields to avoid byte slice was reused. #82
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 I use the latest version(v2.2.0), I got an issue in heavy network I/O.
I'm using
sse
as client, when I send an event stream request to server with headerLast-Event-ID: 0
, server sends lots of events to client, then I found some message's fields, such asID
&Event
, was not the original value.This might be caused by a byte slice was a reference, not a value.
So I use a copied value to these fields (
ID
,Event
,Retry
) to avoid this situation.