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 new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
This is not a new feature request. If it is, please file a feature request instead.
This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
I have a specific, actionable, and well motivated improvement to propose.
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
Improvement Suggestion
with #8514 , to get full gas tracing and execution trace, the node operator needs to enable * LOTUS_VM_ENABLE_TRACING*, which is a breaking behaviour from legacy user from a getting exeuction trace persepctive.
Suggestion: We should:
always generate full execution traces when it's an user iniitated action, i.e, when calling statereplay/statecompute/statecall
rename LOTUS_VM_ENABLE_TRACING to LOTUS_VM_ENABLE_GAS_TRACING and only generate gas tracew when this envvar is enabled.
During normal sync, generate nothing
The text was updated successfully, but these errors were encountered:
Checklist
Ideas
.Lotus component
Improvement Suggestion
with #8514 , to get full gas tracing and execution trace, the node operator needs to enable * LOTUS_VM_ENABLE_TRACING*, which is a breaking behaviour from legacy user from a getting exeuction trace persepctive.
Suggestion: We should:
statereplay
/statecompute
/statecall
LOTUS_VM_ENABLE_TRACING
toLOTUS_VM_ENABLE_GAS_TRACING
and only generate gas tracew when this envvar is enabled.The text was updated successfully, but these errors were encountered: