-
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
ChainIndexer: move lotus-shed chainindex into lotus CLI #12654
Labels
good first issue
Good for newcomers
Comments
Some thoughts on how to attack this:
|
8 tasks
Reopening this because I just realised we have other documentation that refers to the old usage that needs to be updated.
Even the new file, These should all be |
8 tasks
rvagg
added a commit
that referenced
this issue
Nov 20, 2024
rvagg
added a commit
that referenced
this issue
Nov 20, 2024
rjan90
pushed a commit
that referenced
this issue
Nov 26, 2024
rjan90
pushed a commit
that referenced
this issue
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new chain_index.go functionality in lotus-shed is more like a lotus command now than the previous sqlite db management utilities. It interacts via RPC and doesn't do any shonky multi-writer work anymore and our documentation treats it as a normal part of a workflow, so we should just normalise it.
Let's move it into the
lotus
CLI. I think it could either go in under the existingchain
subcommand as anindex
sub-sub command, or it we could just add a new top-levelindex
subcommand in the same DEVELOPER group aschain
.The text was updated successfully, but these errors were encountered: