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
When the size of chain data is big, re-play the whole chain is very difficult.
Without the rollback feature, use binary search to find the commit that introduced a bug is impossible.
As an example, in #1573, when I found the first good commit 9a0bdbd, my chain data was updated.
So, I could not do test again.
I only known the bug is introduced between ad4375b and 9a0bdbd.
Very lucky, there are only 9 commits between ad4375b and 9a0bdbd and 5 of them didn't update codes.
But we won't be so luck forever.
And I tried more times than a binary search could use, wasted me a lot of time.
The text was updated successfully, but these errors were encountered:
Description
When the size of chain data is big, re-play the whole chain is very difficult.
Without the rollback feature, use binary search to find the commit that introduced a bug is impossible.
As an example, in #1573, when I found the first good commit 9a0bdbd, my chain data was updated.
So, I could not do test again.
I only known the bug is introduced between ad4375b and 9a0bdbd.
Very lucky, there are only 9 commits between ad4375b and 9a0bdbd and 5 of them didn't update codes.
But we won't be so luck forever.
And I tried more times than a binary search could use, wasted me a lot of time.
The text was updated successfully, but these errors were encountered: