Fix missing messages_max_size_in_bytes config #182
Merged
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
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.
The
messages_max_size_in_bytesis a config item inCrossSiloMessageConfig.The original design is that when users customize their proxy actor and config, this field should be converted to the corresponding field. E.g. when using grpc proxy, this field should be equivalent to setting "grpc.max_send_message_length" and "grpc.max_receive_message_length" in
GrpcCrossSiloMessageConfig.grpc_channel_options. However, this field get missed when converting toGrpcCrossSiloMessageConfig.This PR fix this bug and should solving #181 and this issue: secretflow/secretflow#952