Eos: get_actions error in version v1.3.0

Created on 26 Sep 2018  路  10Comments  路  Source: EOSIO/eos

when I call the rpc methodget_actions ,it returns me an error in version v1.3.0 which all going well in version v1.2.5. Is it a bug ??? , Tell me what's going wrong , Please ???

Support

Most helpful comment

2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:371 get_actions ] params: {"account_name":"xxxxxx","pos":1,"offset":2} 2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:383 get_actions ] pos: 1 2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:407 get_actions ] start: 1 end: 3 2018-09-25T10:14:26.566 thread-0 http_plugin.cpp:580 handle_exception ] FC Exception encountered while processing history.get_actions 2018-09-25T10:14:26.566 thread-0 http_plugin.cpp:581 handle_exception ] Exception Details: 10 assert_exception: Assert Exception (b & ~1) == 0: {} thread-0 raw.hpp:339 unpack Error unpacking field context_free {"field":"context_free"} thread-0 raw.hpp:368 operator() error unpacking eosio::chain::action_trace {"type":"eosio::chain::action_trace"} thread-0 raw.hpp:616 unpack

All 10 comments

what's error

2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:371 get_actions ] params: {"account_name":"xxxxxx","pos":1,"offset":2} 2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:383 get_actions ] pos: 1 2018-09-25T10:14:26.566 thread-0 history_plugin.cpp:407 get_actions ] start: 1 end: 3 2018-09-25T10:14:26.566 thread-0 http_plugin.cpp:580 handle_exception ] FC Exception encountered while processing history.get_actions 2018-09-25T10:14:26.566 thread-0 http_plugin.cpp:581 handle_exception ] Exception Details: 10 assert_exception: Assert Exception (b & ~1) == 0: {} thread-0 raw.hpp:339 unpack Error unpacking field context_free {"field":"context_free"} thread-0 raw.hpp:368 operator() error unpacking eosio::chain::action_trace {"type":"eosio::chain::action_trace"} thread-0 raw.hpp:616 unpack

hi @heifner , looks like the new field context_free in struct base_action_trace has broken the old data in de-serialization. would you help?

--hard-reply will solve this issue.

--hard-reply will solve this issue.

Even if this solve this issue ,but the efficiency is too low .It will take me some days to fish this. Comparing with reloading the blocks data, it has no any superiority. Is there another way ??

Seeing this across many nodes too. Might need to think about informing the wider BP community about this, as its affecting quite a few apps, especially those that rely on history.

Same error, too.

same error too ,how to fixed

same error too ,how to fixed

--hard-replay-blockchain will solve this issue

I can now confirm that a full --hard-replay from version 1.3.0+ fixes this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

zxf969175364 picture zxf969175364  路  3Comments

christola picture christola  路  3Comments

jcalfee picture jcalfee  路  3Comments

IvanYakimov picture IvanYakimov  路  3Comments

xiaomaogy picture xiaomaogy  路  3Comments