feat(shed): add --db-path and --epoch-file to indexes
events subcommands
#12490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure this is worth merging, but I'm parking this here for now so I don't lose it, it's proven quite helpful.
Taking a clone of an existing database (can be done while running with
sqlite3
on the command-line pointing to the events.db file and running.clone path/to/new/file
), you can then runinspect-events
andbackfill-events
on the cloned file using--db-path
, so you extract data from a lotus node and insert in into an isolated db.--epoch-file
lets me run a specific list of epochs ininspect-events
so I can double-check epochs I'm trying to fix when the list of particularly long.