This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Add optional error_code to transaction and action traces #7108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Resolves #6898.
Rename
parent_action_ordinal
toclosest_unnotified_ancestor_action_ordinal
and remove it from the traces stored by the state history plugin.Consensus Changes
API Changes
Documentation Additions
The new
parent_action_ordinal
field from PR #7044 has been renamed toclosest_unnotified_ancestor_action_ordinal
.New optional field
error_code
has been added toaction_trace
andtransaction_trace
. This field should always be empty if theexcept
field in the same object is empty. However, it is possible forexcept
to be non-empty buterror_code
to be empty (this will be the case for any errors that were not due to theeosio_assert_code
intrinsic). Iferror_code
is non-empty, it means the error was due to an assertion failure on a call toeosio_assert_code
, and the value will be the error code passed into theeosio_assert_code
intrinsic.