-
Notifications
You must be signed in to change notification settings - Fork 110
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
chore(dot/sync): blockQueue
refactored
#2563
Conversation
Codecov Report
@@ Coverage Diff @@
## development #2563 +/- ##
===============================================
+ Coverage 57.53% 57.64% +0.11%
===============================================
Files 218 218
Lines 28664 28663 -1
===============================================
+ Hits 16491 16523 +32
+ Misses 10485 10455 -30
+ Partials 1688 1685 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
f52f974
to
2a925c9
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.
This makes sense, and looks good.
788cf07
to
2170947
Compare
- Context aware `pop` - Do not block `processReadyBlocks` forever on ctx cancel - Change mapping to hashes set (less memory usage) - Remove unneeded `cap int` field - More explicit variable names in block_queue.go
2170947
to
bb4138f
Compare
Changes
pop
processReadyBlocks
forever on ctx cancelcap int
fieldTests
go test -tags integration github.com/ChainSafe/gossamer/dot/sync
Issues
Done whilst reviewing PR #2261
Primary Reviewer
@edwardmack