-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: View the currently known proving live sectors information #8720
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.
Thanks for the PR!
One suggestion which may make it more useful in the future.
We should also switch proving deadlines
to LiveSectors
; AllSectors are not the right thing to use there.
cmd/lotus-miner/proving.go
Outdated
sectorCount, err := partition.AllSectors.Count() | ||
sectorCount, err := partition.ActiveSectors.Count() | ||
if err != nil { | ||
return err | ||
} | ||
|
||
sectorNumbers, err := partition.AllSectors.All(sectorCount) | ||
sectorNumbers, err := partition.ActiveSectors.All(sectorCount) | ||
if err != nil { |
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.
Let's add a flag all
to this function to give the user the option to get info for AllSectors
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.
maybe AllSectors is useless to the user
@swift-mx Did you push the wrong commit? None of the changes in the latest commit seem to line up with my comments. Let me know if you have any questions :) |
The reason for this PR is that some of our sectors have expired. We want to compress the partitions. But I don't know which one should be compressed. So there is a need |
Related Issues
Proposed Changes
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, testarea
: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps