-
Notifications
You must be signed in to change notification settings - Fork 73
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
SHiP: Auto disable-replay-opts instead of exiting with error #1467
Conversation
… not actually needed for trace data.
libraries/state_history/include/eosio/state_history/serialization.hpp
Outdated
Show resolved
Hide resolved
libraries/state_history/include/eosio/state_history/serialization.hpp
Outdated
Show resolved
Hide resolved
@@ -35,11 +49,27 @@ struct history_context_wrapper { | |||
}; | |||
|
|||
template <typename P, typename T> | |||
history_context_wrapper<std::decay_t<P>, std::decay_t<T>> make_history_context_wrapper(const chainbase::database& db, | |||
const P& context, const T& obj) { | |||
struct history_context_wrapper_stateless { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I would have made history_context_wrapper_stateless
a base of history_context_wrapper
.
the advantage is that the functions accepting a history_context_wrapper_stateless&
would also take a history_context_wrapper&
, although I'm not sure if it would have helped a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Serialization has undergone significant changes. Do we have sufficient existing tests to cover the changes?
We have no unittests and very little integration tests that would test any of the serialization logic. Before 3.2 we had no tests for SHiP. We have separate issues for adding tests for SHiP. I think creating tests for serialization is out of scope for this PR. |
state_history_plugin
to automatically setdisable-replay-opts=true
instead of indicating an error and exiting.disable-replay-opts=true
only whenchain-state-history=true
is enabled as it is not needed ifstate_history_plugin
is running with onlytrace-history=true
enabled.chainbase
when serializing transaction trace data. This verifies thatdisable-replay-opts=true
is not needed if only logging transaction trace data.disable-replay-opts
to be set inconfig.ini
instead of only on the command line.Resolves #1403