This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
contractWatcher not marking headers checked #146
Comments
i-norden
added a commit
that referenced
this issue
Oct 8, 2019
…e any logs at that header but other contracts do
i-norden
added a commit
that referenced
this issue
Oct 11, 2019
…e any logs at that header but other contracts do
i-norden
added a commit
that referenced
this issue
Oct 15, 2019
any logs at that header but other contracts do; test
i-norden
added a commit
that referenced
this issue
Oct 24, 2019
any logs at that header but other contracts do; test
i-norden
added a commit
that referenced
this issue
Oct 28, 2019
any logs at that header but other contracts do; test
i-norden
added a commit
that referenced
this issue
Oct 28, 2019
grizz
pushed a commit
that referenced
this issue
Dec 22, 2019
any logs at that header but other contracts do; test
grizz
pushed a commit
to dipd/vulcanizedb
that referenced
this issue
Dec 28, 2019
…oesnt have any logs at that header but other contracts do; test
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Still tracking down exactly how this happens, but it seems that the contractWatcher does not always mark all headers as checked while running in header mode. Adding a
MarkHeaderCheckedForAll
after all logs have been processed inExecute
appears to correct the issue - otherwise the same headers are continually treated as unchecked on subsequent runs.The text was updated successfully, but these errors were encountered: