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
[ruby] More flexible ENCODE_MAX_NESTING #1493
Comments
For anyone finding this (like I have) - this is still an issue after the recent ubp refactoring in the Ruby library. The protobuf/ruby/ext/google/protobuf_c/message.c Lines 928 to 932 in 0ebbd7d
|
This allows increasing the recursing depth from the default of 64, by setting the "max_recursion_depth" to the desired integer value. This is useful to parse complex nested protobuf messages that otherwise error out with "Error occurred during parsing". Fixes protocolbuffers#1493
This allows increasing the recursing depth from the default of 64, by setting the "max_recursion_depth" to the desired integer value. This is useful to parse complex nested protobuf messages that otherwise error out with "Error occurred during parsing". Fixes protocolbuffers#1493
This allows increasing the recursing depth from the default of 64, by setting the "max_recursion_depth" to the desired integer value. This is useful to encode or decode complex nested protobuf messages that otherwise error out with a RuntimeError or "Error occurred during parsing". Fixes protocolbuffers#1493
This allows increasing the recursing depth from the default of 64, by setting the "max_recursion_depth" to the desired integer value. This is useful to encode or decode complex nested protobuf messages that otherwise error out with a RuntimeError or "Error occurred during parsing". Fixes protocolbuffers#1493
* Message.decode/encode: Add max_recursion_depth option This allows increasing the recursing depth from the default of 64, by setting the "max_recursion_depth" to the desired integer value. This is useful to encode or decode complex nested protobuf messages that otherwise error out with a RuntimeError or "Error occurred during parsing". Fixes #1493 * Address review comments Co-authored-by: Adam Cozzette <acozzette@google.com>
At codebeat we have a legitimate use case for deeply nested protocol buffers - we use these to represent ASTs. We know for sure there are no cycles in our data structures so we wouldn't like to be limited by an arbitrary number we can't change. And we can't since it's set in a header file so without forking a repo and manually changing it there is not much we can do. We would like to kindly request that this constant is turned into a Ruby constant that can be modified by the caller.
The text was updated successfully, but these errors were encountered: