feat(shed): lotus-shed find-msg --count X actor:Method#13117
Merged
Conversation
Search back through the chain to find messages of a particular type and print them out. Also includes the ability to add special cases for more information, currently just PCS3 which will also print out the number of sectors and the proof type.
rjan90
approved these changes
May 9, 2025
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Search back through the chain to find messages of a particular type and print them out. Also includes the ability to add special cases for more information, currently just PCS3 which will also print out the number of sectors and the proof type.
This has been sitting in my local repo and I've been hardwiring values but I keep on having to use it so I made it more generic and will check it in.
@rjan90 this is one of the recent uses I've had for this tool so we can look at batch vs aggregate onboarding: