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

teosd may not be able to bootstrap in pruned mode if the chain is far ahead #209

Closed
sr-gi opened this issue Mar 28, 2023 · 0 comments · Fixed by #216
Closed

teosd may not be able to bootstrap in pruned mode if the chain is far ahead #209

sr-gi opened this issue Mar 28, 2023 · 0 comments · Fixed by #216
Labels
bug Something isn't working

Comments

@sr-gi
Copy link
Member

sr-gi commented Mar 28, 2023

Bootstrapping a tower with existing data that has fallen far behind the current chain tip in pruned mode raises an error when fetching block data. This is due to the tower querying the backend about already pruned blocks.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: BlockSourceError { kind: Transient, error: Custom { kind: Other, error: "Block not available (pruned data)" } }', teos/src/main.rs:51:65
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

We should add a flag to bypass this if necessary, making the tower bootstrap from the current tip or from a block with existing data. Notice this may be unsafe, given the tower will be missing some transitions, but if it has fallen far behind some of the triggers may already have expired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant