Skip to content
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

fix(nitro): reorg fix and minor refactoring #17

Merged
merged 4 commits into from
Jul 29, 2024

Conversation

emilianobonassi
Copy link

Overview

Mainly this disable by default to re-org in case of celestia read failures (e.g. node not available or rpc call erroring). Can force to re-org setting explicitely --celestia-cfg.dangerous-reorg-on-read-failure=true.

Minors:

  • return error (instead of nil) in case of unmarshal error on GetProof
  • refactor read client usage

Copy link
Collaborator

@Ferret-san Ferret-san left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can achieve the desired behavior with some changes in the error handling and perhaps opting for this reorg fix only on certain scenarios

das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
das/celestia/celestia.go Show resolved Hide resolved
@Ferret-san Ferret-san merged commit 5a9e7a0 into celestiaorg:celestia-v2.3.3 Jul 29, 2024
2 of 6 checks passed
Ferret-san pushed a commit that referenced this pull request Aug 27, 2024
* Run CI on integration branch
* CI: separate build and test-go-deps steps
* CI: set timeout to 20min for challeng tests
They often take more than 10 minutes (which is the default).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants