Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

Correctly identify missing headers after contract watcher restart #143

Merged
merged 2 commits into from
Sep 24, 2019

Conversation

rmulhol
Copy link
Contributor

@rmulhol rmulhol commented Sep 23, 2019

Resolves #142

Note: built on top of #139 - will need to rebase after that's merged for a proper diff.

@rmulhol rmulhol changed the title Contract watcher missing headers Correctly identify missing headers after contract watcher restart Sep 23, 2019
@rmulhol rmulhol force-pushed the contract-watcher-missing-headers branch from d62fae6 to 3ad0101 Compare September 23, 2019 21:00
Copy link
Collaborator

@i-norden i-norden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I will create an issue to address how this affects method polling and what needs to be done there.

- Previously, we required that the first missing header match the
  configured starting block number. This helps guarantee that we have
  the necessary data for method polling in memory, but prevents the
  process from moving forward if restarted after the starting block
  has already been checked.
@rmulhol rmulhol merged commit ba4e79f into staging Sep 24, 2019
@rmulhol rmulhol deleted the contract-watcher-missing-headers branch September 24, 2019 13:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Contract watcher doesn't return missing headers after process killed
3 participants