This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
cleos multisig review error #4395
Comments
arhag
added a commit
that referenced
this issue
Jun 28, 2018
mrmsm
added a commit
to EOS-BP-Developers/EOS-Test-Cave
that referenced
this issue
Jun 29, 2018
Add# eosio.system contract update msig script Note# A serializer time limit error occurs when reviewing large propositions. This issue is documented at EOSIO/eos#4395 and will be included in the v1.0.8 release.
I update my eos code to v1.0.8,but when i use the command of "cleos get block 447",i also get the error. 2399521ms thread-0 http_plugin.cpp:406 handle_exception ] Exception Details: 10 assert_exception: Assert Exception |
@buaapyj: Did you compile nodeos as debug? Are you running it on a slow machine? You can increase the ABI serialization time limit beyond its default of 15 ms using the |
Unresponsive for 170 days. Posted solution remains the best option for serializing large blocks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was testing multisig feature on local machine. Both propose and approve seem work properly, but when I check proposal statue I got below error:
./cleos multisig review tester paykris -p tester@active
3171085ms thread-0 main.cpp:2712 main] Failed with error: Assert Exception (10)
fc::time_point::now() < deadline: serialization time limit 15000us exceeded
Failed to serialize type
Could anyone shine some light on this issue? Since it seems the last execute step does not work as desired(transfer 1 EOS from mymsig to airdrop account). I want to do the transfer after execute, but it seems execute work but transfer.
More info for debugging:
1. Propose:
./cleos multisig propose paykris '[{"actor": "tester", "permission": "active"},{"actor": "user", "permission": "active"}]' '[{"actor": "mymsig", "permission": "active"}]' eosio.token transfer '{"from":"mymsig", "to":"airdrop1", "quantity":"1.0000 EOS", "memo":"Pay kris 1 EOS"}' -p tester@active
executed transaction: cda32229ae841de45fc2693d828240fd89c34197271acb93fdd0d64907aec2ba 240 bytes 1118 us
eosio.msig <= eosio.msig::propose {"proposer":"tester","proposal_name":"paykris","requested":[{"actor":"tester","permission":"active"}...
warning: transaction executed locally, but may not be confirmed by the network yet
2. Approve:
./cleos multisig approve tester paykris '{"actor": "tester", "permission": "active"}' -p tester@active
executed transaction: 25c38c2219248ffffe2ba9222c8cbab2832fecb748651af54ddcf2b4097d3523 128 bytes 530 us
eosio.msig <= eosio.msig::approve {"proposer":"tester","proposal_name":"paykris","level":{"actor":"tester","permission":"active"}}
warning: transaction executed locally, but may not be confirmed by the network yet
./cleos multisig approve tester paykris '{"actor": "user", "permission": "active"}' -p user@active
executed transaction: cfd468771c44f6e16c55c749e8039ede466ce3adcc5d1ab50ef6a0b9266f11f6 128 bytes 540 us
eosio.msig <= eosio.msig::approve {"proposer":"tester","proposal_name":"paykris","level":{"actor":"user","permission":"active"}}
warning: transaction executed locally, but may not be confirmed by the network yet
3. Execute:
./cleos multisig exec tester paykris -p tester@active
executed transaction: fab338bfe629f600443dd3313ced559c445d2983abb8bbd664e7e651d2729647 160 bytes 692 us
eosio.msig <= eosio.msig::exec {"proposer":"tester","proposal_name":"paykris","executer":"tester"}
warning: transaction executed locally, but may not be confirmed by the network yet
Note that though execute step return a transaction, mysig account does not transfer to airdrop desired number of EOS:
./cleos get table eosio.token airdrop1 accounts
{
"rows": [],
"more": false
}
./cleos get table eosio.token mymsig accounts
{
"rows": [{
"balance": "10.0000 EOS"
}
],
"more": false
}
The text was updated successfully, but these errors were encountered: