-
Notifications
You must be signed in to change notification settings - Fork 111
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
fix(scan): Fix minor concurrency bug in the scan
gRPC method
#8303
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eys are sent on the watch channel
Joins register/subscribe scan service calls, sends SubscribeResults request first, and filters out duplicate results from channel
arya2
added
A-rpc
Area: Remote Procedure Call interfaces
A-concurrency
Area: Async code, needs extra work to make it work properly.
A-blockchain-scanner
Area: Blockchain scanner of shielded transactions
P-Medium ⚡
labels
Feb 21, 2024
arya2
changed the title
fix(scan): Fixes a concurrency bug in the
fix(scan): Fix minor concurrency bug in the Feb 21, 2024
scan
gRPC methodscan
gRPC method
oxarbitrage
approved these changes
Feb 21, 2024
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.
Looks good.
9 tasks
idky137
pushed a commit
to idky137/zebra
that referenced
this pull request
Feb 28, 2024
…Foundation#8303) * update scan task to notify subscribe caller once the new subscribed_keys are sent on the watch channel * Fixes timing bug in scan gRPC method: Joins register/subscribe scan service calls, sends SubscribeResults request first, and filters out duplicate results from channel * Removes outdated TODO * wraps subscribed_keys in an Arc before sending to watch channel, fixes typo * Remove result senders for keys that have been removed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-blockchain-scanner
Area: Blockchain scanner of shielded transactions
A-concurrency
Area: Async code, needs extra work to make it work properly.
A-rpc
Area: Remote Procedure Call interfaces
C-bug
Category: This is a bug
P-Medium ⚡
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This PR is a follow up to #8268 and fixes an issue around missing results from a block in the
scan
gRPC method response.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
subscribed_keys
collection and sending it to the watch channel (and sending it the result receiver)subscribed_keys
in watch channel before writing results to storagescan()
gRPC method to:ScanService
with aSubscribeResults
request and to wait for the response before calling the scan service with aResults
requestresult_receiver
channel to filter out any duplicates from theResults
responseRelated cleanups:
RegisterKeys
andSubscribeResults
service call futuresReview
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
scan()
method is present and unique