Skip to content
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): lotus-shed sectors dump-sectors #12703

Merged
merged 1 commit into from
Nov 22, 2024
Merged

Conversation

rvagg
Copy link
Member

@rvagg rvagg commented Nov 19, 2024

Most of the fields in SectorOnChainInfo for all of the records on chain (using the power actor to list miners and then listing all of their sectors). No filtering so far, output as CSV. Currently doesn't print the two CIDs. This came up as part of the FIP-0096 (or whatever number this will get filecoin-project/FIPs#1079) discussions looking at termination fees and I wanted to collect some data for it.

@rvagg rvagg requested a review from ZenGround0 November 19, 2024 07:28
@rvagg rvagg added the skip/changelog This change does not require CHANGELOG.md update label Nov 19, 2024
Copy link
Contributor

@ZenGround0 ZenGround0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main shed command looks fine but Id like to understand why you are changing
the loadChainStore function to explicitly assume splitstore things.

cmd/lotus-shed/state-stats.go Show resolved Hide resolved
@rvagg rvagg enabled auto-merge (squash) November 22, 2024 03:07
@rvagg rvagg merged commit 9548629 into master Nov 22, 2024
87 checks passed
@rvagg rvagg deleted the rvagg/dump-sectors branch November 22, 2024 03:07
virajbhartiya pushed a commit to virajbhartiya/lotus that referenced this pull request Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip/changelog This change does not require CHANGELOG.md update
Projects
Status: ☑️ Done (Archive)
Development

Successfully merging this pull request may close these issues.

2 participants