Implementation of transaction dry run #2380
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
steelgeek091
requested review from
jolestar,
wow-sven,
geometryolife,
baichuan3,
popcnt1 and
pause125
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
jolestar
reviewed
Aug 7, 2024
steelgeek091
commented
Aug 8, 2024
return error info when dry run execution function finish the dry_run finish the transaction dry run while publishing the transaction remove debug code in counter example remove unused parameter execute the action directly instead sign it
steelgeek091
force-pushed
the
dry_run_transaction
branch
from
4dbbb4b
to
9d9931e
Compare
jolestar
reviewed
Aug 8, 2024
|
建议 |
jolestar
approved these changes
Aug 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When publishing the module, perform a dry run. If an error occurs, stop and report the following error:
Transaction dry run failed: "VMError with status ABORTED with sub status 6789 at location Module ModuleId { address: 285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d, name: Identifier("counter") } and message 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::f5 at offset 1 at code offset 1 in function definition 4"
CallStack trace:
0 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::f4.0
1 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::f3.0
2 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::f2.0
3 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::f1.0
4 0x285529d7fd13ffcda9d89cd250b4025ba9226c0e2e57f5ca3d739cb236dc259d::counter::init.6
Do we need to dry run trasaction when executing normal transaction?