Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

get_actions error in version v1.3.0 #5818

Closed
somebodyLi opened this issue Sep 26, 2018 · 10 comments
Closed

get_actions error in version v1.3.0 #5818

somebodyLi opened this issue Sep 26, 2018 · 10 comments
Assignees
Labels

Comments

@somebodyLi
Copy link

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 ???

@SpadeRoy
Copy link

what's error

@somebodyLi
Copy link
Author

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

@taokayan
Copy link
Contributor

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?

@taokayan
Copy link
Contributor

--hard-reply will solve this issue.

@somebodyLi
Copy link
Author

--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 ??

@pete001
Copy link

pete001 commented Oct 3, 2018

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.

@ghost
Copy link

ghost commented Oct 8, 2018

Same error, too.

@hmilymb
Copy link

hmilymb commented Oct 9, 2018

same error too ,how to fixed

@somebodyLi
Copy link
Author

somebodyLi commented Oct 10, 2018

same error too ,how to fixed

--hard-replay-blockchain will solve this issue

@pete001
Copy link

pete001 commented Oct 10, 2018

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

matthewdarwin added a commit to EOS-Nation/bpvalidate that referenced this issue Oct 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants