-
Notifications
You must be signed in to change notification settings - Fork 1.3k
feat(exec): dump intermediate cache blocks from FVM exec in StateReplay #12822
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
base: master
Are you sure you want to change the base?
Conversation
Added an inspection of the With my node running with
|
This is beautiful |
0f4fc44
to
6c98b11
Compare
* Plumb through dump_cache from fvm4 to access intermediate blocks: - filecoin-project/filecoin-ffi#512 - filecoin-project/ref-fvm#2101 * Enable cache dumping in StateReplay with LOTUS_REPLAY_DUMP_CACHED_BLOCKS * Add optional "Blocks" field InvocResult * Handle ExecutionEvent::Log's and add "Logs" field to ExecutionTrace * Dump intermediate cache blocks to CAR in /tmp when they appear while using `lotus-shed msg --exec-trace`.
6c98b11
to
1fbd28e
Compare
This is back on the menu again! With filecoin-project/ref-fvm#2101 and filecoin-project/ref-fvm#2113 merged, filecoin-project/filecoin-ffi#512 is now depending on ref-fvm master and it all works!
It's now much less noisy when you run it with default args, just json output of the pieces it can give you. But |
1fbd28e
to
fb473a5
Compare
lotus-shed msg --exec-trace
.As with filecoin-project/filecoin-ffi#512, I may bail on some or all of this, it's a little bit janky (but it is for debugging!). But the
ExecutionEvent::Log
thing probably needs to stay, so that may become a new PR.