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

[NIT-2803] Raise error when db is missing the chain config #2684

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gligneul
Copy link
Contributor

If the chain config is missing from the database, it is probably corrupt and the user should take action instead of letting the initialization code run.

@cla-bot cla-bot bot added the s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA. label Sep 19, 2024
@gligneul
Copy link
Contributor Author

I recommend checking "hide whitespace" when reading the diff.

If the chain config is missing from the database, it is probably corrupt
and the user should take action instead of letting the initialization
code run.
@gligneul gligneul force-pushed the gligneul/database-missing-chain-config branch from 8dad450 to 3d1ee13 Compare September 19, 2024 13:52
@gligneul gligneul changed the title Raise error when db is missing the chain config [NIT-2803] Raise error when db is missing the chain config Sep 19, 2024
@PlasmaPower
Copy link
Collaborator

I wonder if this would break arbitrum classic state import, as the db exported from arbitrum classic probably doesn't have a chain config

@gligneul
Copy link
Contributor Author

I wonder if this would break arbitrum classic state import, as the db exported from arbitrum classic probably doesn't have a chain config

Good point. I will see how to test it and report back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants