Failure: Received message larger than max

MacOS Catalina, 10.15.5, bazel 3.4.1. (setup was perfectly smooth)
Created example with
bazel-bin/generate_dummy_data \
--server_data_file=/tmp/dummy_server_data.csv \
--client_data_file=/tmp/dummy_client_data.csv --server_data_size=10000 \
--client_data_size=10000 --intersection_size=800 --max_associated_value=100

Client failed, saying:
Client: Loading data...
Client: Generating keys...
Client: Starting the protocol.
Client: Waiting for response and encrypted set from the server...
Client: Received encrypted set from the server, double encrypting...
Client: Sending double encrypted server data and single-encrypted client data to the server.
Client: Waiting for encrypted intersection sum...
Client::ExecuteProtocol: failed to ReEncryptSet: 13: GrpcClientMessageSink: Failed to send message, error code: 8, error_message: Received message larger than max (6540031 vs. 4194304)

Reproduce the failure with bazel-bin/generate_dummy_data using the command and data sizes in the report, then trace the client failure from ExecuteProtocol through ReEncryptSet. The work is done when this input completes without the gRPC “Received message larger than max” error and the protocol reports the encrypted intersection sum.

Written by the indexing model from the issue text.