-
Notifications
You must be signed in to change notification settings - Fork 212
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
request body too large from install-bundle / 400 from agoric publish #6454
Comments
The rejected bundle is 750K. |
Parameter in |
I think multiple megabytes are sensible as long as we take payment based on content-length up front and drop the request if it exceeds its advertised content-length without a refund. |
@michaelfig suggested that some network operation parameter outside the SDK was the limitation here. Whatever it was seems to have gone away. It's working today:
Then in a REPL, started with
|
This seems to be back... or something very much like it: I'm getting
Using agd, it looks like...
I suspect this blocks #6099. The earlier fragmentation an reassembly work-around is based on ag-solo access, which we won't have in production. |
tried it on a local node state-sync'd from devnet; no joy:
|
changed
where 21 is...
aka
|
On second thought, let's make a separate issue for the |
JSON RPC is doubling the request sizeI'm failing to install a bundle that's 0.607 MB compressed:
with help from @gibson042 , we looked at the traffic using
A bundle that's 0.408 MB compressed works:
For reference, size details:
context: I'm working on... |
Describe the bug
I can't publish the 1.3M
psm
bundle.The 836K
mintHolder
bundle works.To Reproduce
I haven't tried to reproduce it, but this is what I did:
so we tried agd and got a little more diagnostics:
Expected behavior
the bundle gets published and visible from
agoric follow :bundles
Platform Environment
loadtest
git describe --tags --always
)@agoric/cache@0.2.2-16-g438777d61 (a dev branch; changes are most likely unrelated)
cc @kriskowal
The text was updated successfully, but these errors were encountered: