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

[Bug]: "grpc: received message larger than max" when get specified tx info #3151

Closed
1 task done
toolchainx opened this issue Jun 18, 2024 · 3 comments
Closed
1 task done
Labels
general questions other: decayed Stale issues that need follow up from commentators. Were closed for inactivity

Comments

@toolchainx
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

The following result happens when I request every public/private Gaiad node (including our private Gaiad node) that I can find

curl https://cosmos-rest.publicnode.com/cosmos/tx/v1beta1/txs/961DCEE84F52AA641914E15C74ABC638E5D481CF27C197BB3DEFB3AA9DDFF43D
{"code":8,"message":"grpc: received message larger than max (10796134 vs. 10485760)","details":[]}

Gaia Version

v17.2.0

How to reproduce?

curl https://cosmos-rest.publicnode.com/cosmos/tx/v1beta1/txs/961DCEE84F52AA641914E15C74ABC638E5D481CF27C197BB3DEFB3AA9DDFF43D
@toolchainx toolchainx added status: waiting-triage This issue/PR has not yet been triaged by the team. type: bug Issues that need priority attention -- something isn't working labels Jun 18, 2024
@Reecepbcups
Copy link
Member

Reecepbcups commented Jun 18, 2024

@toolchainx You need to modify your app.toml [grpc] max-recv-msg-size to be larger than 10485760 (10mb) on your private node

image

@MSalopek MSalopek added general questions and removed type: bug Issues that need priority attention -- something isn't working status: waiting-triage This issue/PR has not yet been triaged by the team. labels Jun 20, 2024
@MSalopek
Copy link
Contributor

Please let us know if the suggestion above fixed your issue?

@MSalopek MSalopek added the other: decayed Stale issues that need follow up from commentators. Were closed for inactivity label Jul 4, 2024
@MSalopek
Copy link
Contributor

Closing as there's no activity.
The fix above should mitigate the reported issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
general questions other: decayed Stale issues that need follow up from commentators. Were closed for inactivity
Projects
Status: 👍 F4: Assessment
Development

No branches or pull requests

3 participants