fix(node-loader): Fix anoying error with too large RPC data #3162
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
techraed
added
A0-pleasereview
breathx
approved these changes
Aug 23, 2023
techraed
added
A2-mergeoncegreen
shamilsan
approved these changes
Aug 24, 2023
clearloop
approved these changes
Aug 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pretty frequently we receive an RPC error, which tell us that RPC payload is too big. This fixes the client side of that error.
Server side is "fixed" with running the node (loaded by
gear-node-loader) with--rpc-max-response-size 100cli param.@gear-tech/dev