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
No way to configure max inbound message size in DAML Script #5992
Comments
I believe the value is respected, but you are actually causing the maximum outbound message threshold to be hit. Unfortunately this option is not yet configurable. |
You could easily test my claim by reducing the inbound message size to a 1KB and trying to upload a fairly sizable DAR (remember that the inbound message size applies to compressed payloads, so make sure the DAR is ~1MB in size to be on the safe side). |
|
Verified that this is indeed an issue in DAML Script, I’ll add an option to make the size configurable. |
Ah, thanks. |
Yep, it's a DAML Script issue. However, I would in that case expect the command to go through as the error only occurs on the "return path". However, it doesn't, and the Sandbox shows the below errors. This suggests to me that I'd get different behaviour when submitting via
|
I've opened a separate ticket for the above: #5995 |
Fixed in #5996 |
Using the code in #5947 with
n=50000
, I can generate large transactions which cause the default gRPC message size limit to be exceeded. Trying to increase this with the--maxInboundMessageSize
flag does not work in ether sandbox or sandbox classic.To start Sandbox:
then upload dar with
daml ledger upload-dar
, and finally run the scenario.The error received is
This suggests the flag was not applied.
Interesting side-note: The actual message size is twice as big in Sandbox (27317398) as in Sandbox classic (13155912).
The text was updated successfully, but these errors were encountered: