docs: add FAQ question for wrong Block.Header.Version #1546
docs: add FAQ question for wrong Block.Header.Version #1546jcstein merged 2 commits intocelestiaorg:mainfrom
Conversation
WalkthroughThe recent updates focus on enhancing node stability during network upgrades by providing detailed instructions for handling consensus failures due to invalid block versions. These instructions include updating the node's binary, using specific startup flags, and performing a reset if necessary to ensure smooth operation and synchronization with the network. Changes
Recent Review DetailsConfiguration used: CodeRabbit UI Files selected for processing (2)
Additional Context UsedLanguageTool (106)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| ``` | ||
|
|
||
| then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. |
There was a problem hiding this comment.
Ensure the error message starts with a capital letter and consider adding a comma before 'but'.
- then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade.
+ Then it is likely that the network has upgraded to a new app version, but your consensus node was not prepared for the upgrade.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| ``` | |
| then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. | |
| Then it is likely that the network has upgraded to a new app version, but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. |
| ``` | ||
|
|
||
| then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. |
There was a problem hiding this comment.
Ensure the error message starts with a capital letter and consider adding a comma before 'but'.
- then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade.
+ Then it is likely that the network has upgraded to a new app version, but your consensus node was not prepared for the upgrade.Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
| ``` | |
| then it is likely that the network has upgraded to a new app version but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. | |
| Then it is likely that the network has upgraded to a new app version, but your consensus node was not prepared for the upgrade. To fix this, you'll need to update your binary to the latest version and restart your node with the relevant `--v2-upgrade-height` for the network you're running on. If your node still can't sync to the tip of the chain after the above steps, consider a `celestia-appd tendermint unsafe-reset-all` to reset your node and start syncing from the genesis block. |
|
i knew i shouldn't have trusted coderabbit. thank you @rootulp |
2 participants
The useful content got deleted from #1545 before merging.
Summary by CodeRabbit