We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The publishBundle provided by agoric-cli in the deployPowers (added in #4975) seem to not handled errors correctly:
publishBundle
agoric-cli
deployPowers
account sequence mismatch
Steps to reproduce the behavior:
SDK_SRC=/path/to/agoric-sdk ./start.sh
Successful loadgen
@kriskowal mentions that we should handle both failures of sending the bundle to the chain, and failure of the bundle to be installed on the chain.
agoric: deploy: /workspaces/agoric/agoric-sdk/golang/cosmos/build/agd tx swingset install-bundle --gas auto --gas-adjustment 1.2 --home /workspaces/agoric/testnet-load-generator/_agstate/agoric-servers/local-solo-8000/ag-cosmos-helper-statedir --keyring-backend test --from ag-solo --chain-id agoric --yes @/tmp/agoric-cli-bundle--21515-uAC3PJ5CCakJ/bundle.json Error: rpc error: code = InvalidArgument desc = account sequence mismatch, expected 14, got 13: incorrect account sequence: invalid request Usage: agd tx swingset install-bundle <JSON>/@<FILE>/- [flags]
The text was updated successfully, but these errors were encountered:
kriskowal
Successfully merging a pull request may close this issue.
Describe the bug
The
publishBundle
provided byagoric-cli
in thedeployPowers
(added in #4975) seem to not handled errors correctly:account sequence mismatch
error, and there is no retry logicpublishBundle
seem to be fire and forget, claiming success even in the presence of errorsTo Reproduce
Steps to reproduce the behavior:
SDK_SRC=/path/to/agoric-sdk ./start.sh
Expected behavior
Successful loadgen
Additional context
@kriskowal mentions that we should handle both failures of sending the bundle to the chain, and failure of the bundle to be installed on the chain.
Screenshots
The text was updated successfully, but these errors were encountered: