-
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: shed: Add a tool to read data from sectors #10169
Conversation
cmd/lotus-shed/sectors.go
Outdated
} | ||
|
||
func (e *emptyLocalStorage) Stat(path string) (fsutil.FsStat, error) { | ||
//TODO implement me |
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.
What needs implementing here?
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.
Nope, this is just a dummy impl
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.
Remove the comment then?
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 from a high level. Just had a few additional qs
c253839
to
12656b0
Compare
Related Issues
Proposed Changes
Adds a tool to extract data from sectors from a running lotus-miner deployment. This connects to the storage subsystem much like boost would for retrievals and reads raw pieces.
Additional Info
I wanted to debug why some of my deals failed to get indexed by dagstore, but extracting data from sectors was not easy, so I built this tool.
Apparently my deal was all null bytes somehow
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, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps