-
Notifications
You must be signed in to change notification settings - Fork 0
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
a3p integration for liquidation visibility #6
Comments
Error: RPC error -32600 - Invalid Request: error reading request body: http: request body too largeContextAfter starting the container built using the When installing the contract bundle (generated by executing I have made sure that the bundle I provided in the The same behaviour does not happens when I install the bundles on a local chain launched using the This error message point me to the issue #28, but the proposed work around was not useful for me. I am not sure if this issue can be related with the issue #17 Error messageChain Logs:
|
Follow up on the issue described aboveA lead to a possible solution was discussed on office hours, that pointed to a possible source of this error could be the bundle be larger than 1MB. See Agoric/dapp-offer-up#28. To test this case I used the test-build-proposal.js for the created vaultFactory proposal-builder. Based on the test result, we can assume that this is not the issue
As an experiment, I passed the
|
The following commit seems to fix the issue faa0773 Although there was some inconsistent behaviours while I was testing with different approaches. Nonetheless, @alexanderem49 the update above will be enough for you to continue extending the integration test coverage |
Current status:
vaultFactory
proposal, permit and bundle to the assets directory (9179306)test-liquidation-visibility.js
using as guide thetest-crabble-start.js
andadd-collateral.test
(ad0fae5)Note: in order to run the
eval.sh
script it is necessary to first start theagd
, ( @alexanderem49 that is the source of the time-out error you were facing ).For this purpose I end up have 2 open terminals and run the start_agd script in one and the
eval
in the other.I think the
run_eval
script would be able to run both processes but it was confusing to follow the log messages.Task: confirm with @anilhelvaci if this is the correct flow to setup the env and execute the test
The text was updated successfully, but these errors were encountered: