Skip to content
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

[KS-372] Lazy initialize the registrysyncer #13787

Merged
merged 1 commit into from
Jul 9, 2024

Conversation

cedric-cordenier
Copy link
Contributor

Requires Dependencies

Resolves Dependencies

@cedric-cordenier cedric-cordenier force-pushed the ks-372-no-live-nodes-registrysyncer branch from ae24258 to 72d2111 Compare July 9, 2024 12:56
@cedric-cordenier cedric-cordenier marked this pull request as ready for review July 9, 2024 13:30
@cedric-cordenier cedric-cordenier requested a review from a team as a code owner July 9, 2024 13:30
stopCh services.StopChan
launchers []Launcher
reader types.ContractReader
initReader func(ctx context.Context, lggr logger.Logger, relayer contractReaderFactory, registryAddress string) (types.ContractReader, error)
Copy link
Contributor

Choose a reason for hiding this comment

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

/nit: it doesn't seem like this can be set by any caller. iiuc, then there would be less indirection to simply make it a static method on the syncer, or omit it entirely and call newReader in it's place

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added this mainly to make testing easier, such that a test could set initReader and set up a mock rather than setting up an actual chain reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants