Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grpc: fix receiving empty messages when compression is enabled and maxReceiveMessageSize is maxInt64 #7753 #7914

Conversation

vinothkumarr227
Copy link

Fixes #4552

RELEASE NOTES:

grpc: fix receiving empty messages when compression is enabled and maxReceiveMessageSize is maxInt64

Copy link

linux-foundation-easycla bot commented Dec 10, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

@arjan-bal arjan-bal requested review from purnesh42H and removed request for purnesh42H December 10, 2024 09:55
@arjan-bal
Copy link
Contributor

@vinothkumarr227 can you please squash the commits before we start reviewing the PR?

@vinothkumarr227
Copy link
Author

can you please squash the commits before we start reviewing the PR?

Sure, I will do it

@vinothkumarr227 vinothkumarr227 force-pushed the 4552-empty-response-on-enable-decompression branch from ae27ab0 to a3b77c9 Compare December 10, 2024 11:10
@vinothkumarr227
Copy link
Author

I worked on Vivek's branch for the changes related to pull request #7914, but encountered permission and merge conflicts. I have now created a new branch from master, updated the code, and will be closing this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get empty response when compress enabled and maxReceiveMessageSize be maxInt64
3 participants