-
Notifications
You must be signed in to change notification settings - Fork 215
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
[Merged by Bors] - use first applied block in epoch for new miner active set #4997
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #4997 +/- ##
=======================================
Coverage 77.1% 77.1%
=======================================
Files 254 254
Lines 30355 30385 +30
=======================================
+ Hits 23430 23457 +27
- Misses 5404 5405 +1
- Partials 1521 1523 +2
|
8b84a98
to
3631e6a
Compare
miner/util.go
Outdated
} | ||
|
||
func ActiveSetFromEpochFirstBlock(db sql.Executor, epoch types.EpochID) ([]types.ATXID, error) { | ||
result, err := ActiveSetFromEpochFirstCertifiedBlock(db, epoch) |
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 would be a different block for synced node, i think it should be always first applied regardless of certificate
i think it is this bug #4912 |
not aware of this. thanks! |
bors merge |
## Motivation Closes #4912 ## Changes - for new miner use the first applied block for ref ballot active set
Build failed: |
bors merge |
## Motivation Closes #4912 ## Changes - for new miner use the first applied block for ref ballot active set
Pull request successfully merged into develop. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
## Motivation follow up on #4997 doing the same for hare active set
Motivation
Closes #4912
Changes