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
Currently, we log when a message fails but it can be difficult to figure out what the exact message was. Whenever a message fails, we should log enough information to replicate the failure:
The current height, parent tipset, and parent state.
The number of previously applied messages.
We could also consider logging this in a big batch of "failed messages" after computing a tipset? But that may not be necessary.
The text was updated successfully, but these errors were encountered:
Simulation branch: #6406
Currently, we log when a message fails but it can be difficult to figure out what the exact message was. Whenever a message fails, we should log enough information to replicate the failure:
We could also consider logging this in a big batch of "failed messages" after computing a tipset? But that may not be necessary.
The text was updated successfully, but these errors were encountered: