-
Notifications
You must be signed in to change notification settings - Fork 117
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(scan): Handle RegisterKeys messages in scan task #8222
Conversation
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.
utACK
Looks great. I think we can merge and refactor later on if we need to.
1c4bf90
to
6a45930
Compare
2059397
to
64e682c
Compare
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.
I think this looks really good, i sent a few suggestions and questions but they are all minors.
…heck if there is no key height for a key in `parsed_keys`
afb9a05
to
217fcda
Compare
Motivation
This PR handles
RegisterKey
messages in the scan task, adding the new keys toparsed_keys
to be scanned, and spawning a task to scan past blocks for the new viewing keys.Closes #8220.
PR Author Checklist
Check before marking the PR as ready for review:
For significant changes:
If a checkbox isn't relevant to the PR, mark it as done.
Solution
ScanTask
to its own module in theservice
moduleprocess_messages()
to take a mutable reference toparsed_keys
and return new keysscan_until()
functionscan_until_task_handler
to poll aFuturesUnordered
of scanner tasksTesting
process_messages()
is behaving as expectedscans_for_new_key
test #8236)Review
Anyone can review.
Reviewer Checklist
Check before approving the PR:
PR blockers can be dealt with in new tickets or PRs.
And check the PR Author checklist is complete.
Follow Up Work
scans_for_new_key
test #8236