Fix bug of handle large rpc call response #46
+14
−7
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.
If the response of rpc call is separate into serval fragments, will trying to hold them and merge into ONE buffer.
This bug will happen when using this client to download large files.
Here is some log when I download a file with 160MB. It has a large rpc call, and separated into 9 fragments. In old version,
![image](https://user-images.githubusercontent.com/7711142/197766545-5311a191-8996-4142-92a6-c65fc151419f.png)
_recordLength is adds up but buffer didn't hold bytes all