-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add DiscoveryProcessor to commit plugin. #141
Conversation
fe0af79
to
4ee5e32
Compare
4ee5e32
to
acea493
Compare
Test Coverage
|
if err != nil { | ||
p.lggr.Errorw("failed to discover contracts", "err", err) | ||
} | ||
if !p.contractsInitialized { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If contract addresses change, is there a risk of having stale addresses?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Contract addresses won't change but we could have new chains added while the plugin is running.
However, the discovery processor continuously discovers new addresses at the moment, so these new chains get picked up. There's also a test for this in chainlink.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A new address would be a problem because we don't unbind the old one and currently ensure that there is only one bound address. This is something we could support pretty easily if we need to in the future.
Add contract discovery to the commit plugin.