You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a security-related bug/issue. If it is, please follow please follow the security policy.
This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
This is not a new feature request. If it is, please file a feature request instead.
This is not an enhancement request. If it is, please file a improvement suggestion instead.
I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
I did not make any code changes to lotus.
Lotus component
lotus daemon - chain sync
lotus miner - mining and block production
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt)
lotus miner/market - storage deal
lotus miner/market - retrieval deal
lotus miner/market - data transfer
lotus client
lotus JSON-RPC API
lotus message management (mpool)
Other
Lotus Version
Daemon: 1.15.2-dev+interopnet+git.0295d2274.dirty+api1.5.0
Local: lotus version 1.15.2-dev+interopnet+git.0295d2274.dirty
Describe the Bug
When running lotus state compute-state --html, the output contains the error ERROR: template: message:3:24: executing "message" at <.Msg.To>: nil pointer evaluating *types.Message.To.
This error only occurs when looking at the state after the FVM upgrade (3000 on interopnet).
Logging Information
.
Repo Steps
lotus state compute-state --html
The text was updated successfully, but these errors were encountered:
So, the issue is likely that execution tracing wasn't enabled for this message. Due to how execution tracing currently works in the FVM, we'll end up with an "empty" message.
The lotus VM would always include the root message, even when tracing was disabled.
@jennijuju No, we expect the issue to exist in all cases (before this fix) -- the problem is that we were only trying to set the execution trace if we had an FVM execution trace (which we did when we had LOTUS_VM_ENABLE_GAS_TRACING_VERY_SLOW=1).
Checklist
Latest release
, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Describe the Bug
When running
lotus state compute-state --html
, the output contains the errorERROR: template: message:3:24: executing "message" at <.Msg.To>: nil pointer evaluating *types.Message.To
.This error only occurs when looking at the state after the FVM upgrade (3000 on interopnet).
Logging Information
Repo Steps
lotus state compute-state --html
The text was updated successfully, but these errors were encountered: