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

Allow specifying since flag for Carp #95

Open
SebastienGllmt opened this issue Jul 12, 2022 · 3 comments
Open

Allow specifying since flag for Carp #95

SebastienGllmt opened this issue Jul 12, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@SebastienGllmt
Copy link
Contributor

This is another change we want users to be able to specify in their config. Currently we pass since: None to Oura, but this should be configurable. The solution for this is going to be the same solution as the BearerKind ticket: #34

@SebastienGllmt SebastienGllmt added the enhancement New feature or request label Jul 12, 2022
@SebastienGllmt
Copy link
Contributor Author

SebastienGllmt commented Aug 7, 2022

We already have a start_block undocumented parameter in the main indexer crate so it may be good to formalize it

@bakon11
Copy link

bakon11 commented Mar 18, 2023

Hi,

I tried using start block, but when I feed it a block that doesn't exist in the DB yet, it gives me an error saying that exactly.

Block hash does not exist in database

Is this flag only when you've already synced everything and want to sync extra data when changes to execution plan have been made?

Thanks.

@tdedgx
Copy link

tdedgx commented Jul 28, 2023

upvote! I asked for something similar in discord spt not sure if you saw that. I still cant get it to start from a certain block, tried setting start_block directly in the indexer, and using execution plan with readonly tasks. Complains about missing blocks and exits. Formalising this to work as a config property is a necessary upgrade
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants