Execution journal entries on entry point calls #5354
Merged
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.
The node now produces:
TransformKindV2::EntryPointCalledexecute result whenever wasm session code or a contract attempts to do an entry point call. This also applies to VM2 constructor and upgrade method calls.TransformKindV2::EntryPointCalledis not stored to global stateTransformKindV2::Ret(RetValue::Unit)execution journal entry if the contract didn't call thereturnfunctionality on it's own.returnfunctionality and passed no output, there will be aTransformKindV2::Ret(RetValue::Unit)execution journal entry