-
Notifications
You must be signed in to change notification settings - Fork 604
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
pubsub: gRPC max recv set to 4MB #2190
Comments
That module is on version 0.9.0 now. Can you try upgrading? |
I made a typo when filling out this ticket, I am on version 0.9.0 not 0.3.0. So it's still failing there. |
Also confirmed by looking at node_modules, I see the change made on the gRPC side common-grpc/src/service.js, so it's definitely pulled in. Could this be an issue on PubSub server side? |
Thanks for confirming. @murgatroid99 I tried to remove the message limit with the changes in this PR: #2007 -- did I make a mistake, or could this error be coming from the API response? |
The options that you add in that PR are gRPC Client constructor arguments. They are supposed to be in the same object as the |
Gotcha, thanks! |
PR sent with a fix in #2192 -- good catch @chrisgoffinet! |
Reproduce steps:
@google-cloud/pubsub:
0.3.00.9.0Publish message > 4MB to a topic
Retrieve message through subscription: Error: Received message larger than max (6374241 vs. 4194304)
#2007 was pushed to fix the limits but the existing PubSub client seems to be still defaulting to 4MB. It was originally posted about on #1991 which was closed after #2007 was merged but still throwing that error.
The text was updated successfully, but these errors were encountered: