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
@heifner do you know of a way to reliably reproduce this issue?
I'm wondering if this issue could be caused by this, where we first call abort_block();, which calls _time_tracker.clear();, and then maybe_switch_forks(), which time may be counted in other?
I don't know of a way to reproduce it. Maybe spam a node with set_code or other heavy transactions (jumborow or eosmechanics cpu maybe) to cause a speculative block to be exhausted.
I think likely did find the issue as the timer should be reset after the maybe_switch_forks.
Looks like the total time of
427393
and theother
time of91176
includes the processing of the incoming block:Not sure if this is always incorrect or only when restarting a speculative block:
The text was updated successfully, but these errors were encountered: