-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
LogPoller CLI command to resolve reorg greater than finality depth #12867
Merged
prashantkumar1982
merged 11 commits into
develop
from
feature/BCI-2981-logpoller-resolve-reorg
Apr 26, 2024
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
19f3e11
find lca and remove block after CLI
dhaidashenko a1397e4
fix sort.Find typo
dhaidashenko 08ed233
make RemoveBlocks local cmd
dhaidashenko 86ead9a
tests
dhaidashenko d513e0c
added changeset
dhaidashenko 8af2e3e
added tags to the changeset
dhaidashenko 6dbf9a2
fixed tests
dhaidashenko 47a2232
Merge branch 'develop' into feature/BCI-2981-logpoller-resolve-reorg
dhaidashenko 0913550
make cmds, vars cases consistent
dhaidashenko 2762c32
Merge branch 'feature/BCI-2981-logpoller-resolve-reorg' of github.com…
dhaidashenko 72dc7f5
Merge branch 'develop' into feature/BCI-2981-logpoller-resolve-reorg
dhaidashenko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
--- | ||
"chainlink": minor | ||
--- | ||
|
||
Added a new CLI command, `blocks find-lca,` which finds the latest block that is available in both the database and on the chain for the specified chain. | ||
Added a new CLI command, `node remove-blocks,` which removes all blocks and logs greater than or equal to the specified block number. | ||
#nops #added |
This file contains 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
This file contains 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
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
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 was the rationale behind placing one of these commands under
blocks
and the other one undernode
. Seems like it might be more difficult to find them both if they're not in the same place?Because these are both evm-specific commands, I think they should probably both go under
chainlink chains evm
... although I do notice there are some commands, such aschainlink blocks replay
which are also evm-specific.(We should probably move that one under
chainlink chains evm
soon also. I'll mention that to those more involved with LOOP arch planning.)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.
I agree that it's confusing. I've just tried to follow existing structure of the commands.
Existing
blocks replay
interacts with the LogPoller and triggers it to replay blocks.find-lca
- also interacts with the LogPoller and requests latest good block. Thus it made sense to me to group them together.At the same time
chains evm
simply lists available evm chains.Initially I've planed to have
remove-blocks
in theblocks
section, but realised that it needs unique lock on the database.node
/local
sections seems to contain all commands that must be executed on local node only. It also containsrebroadcast-transactions
, which is EVM/TXM related but still resides here. I figured that all local commands must be grouped together to highlight that they are executed on the local node.Foundations are the owners of this package, so It's up to you to decide where to put the commands.
Should I move them?
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.
Yeah, given that one of them is local and the other isn't I agree that it makes sense to have
remove-blocks
withrebroadcast-transactions
andfind-lca
withreplay
. Unfortunately, I think we're going to want to moveremove-blocks
andrebroadcast-transactions
soon to be underchainlink blocks evm
andchainlink node evm
. So I'm not sure whether it's better to add them now in the same place and move them later, or just add them in the right place now and move the other two later. Asking rest of my team for some advice on that.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.
@dhaidashenko Alright, yeah let's just add them here now and we can move them all together later.