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

Populate consensus_params.version for exported app #3472

Open
rootulp opened this issue May 12, 2024 · 0 comments
Open

Populate consensus_params.version for exported app #3472

rootulp opened this issue May 12, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@rootulp
Copy link
Collaborator

rootulp commented May 12, 2024

Context

#3450 fixed a few issues to make it possible to invoke celestia-appd export

Problem

The exported output doesn't populate consensus_params.version

Note: this isn't a big deal b/c we could populate this field manually.

Proposal

Populate the consensus_params.version field for an exported app.

@rootulp rootulp added the good first issue Good for newcomers label May 12, 2024
rootulp added a commit that referenced this issue May 14, 2024
Closes #3392
Opens #3472

Fixes a few bugs:
1. Previously all modules had `ExportGenesis` invoked on them even if
they weren't supported by the current app version. Now we only call
`ExportGenesis` for the modules that are supported by the current app
version
2. The export command wasn't updated to account for the changes in
#3320 which force us to
mount stores after `app.New()` based on the current app version
3. The minfee module couldn't be exported b/c it didn't register a key
table in `ExportGenesis`

## Testing

I could export an app on app version 1 and 2. See
[output](https://gist.github.com/rootulp/dfea2b5b40f7366b03706fc39321ceee)
0xchainlover pushed a commit to celestia-org/celestia-app that referenced this issue Aug 1, 2024
Closes celestiaorg/celestia-app#3392
Opens celestiaorg/celestia-app#3472

Fixes a few bugs:
1. Previously all modules had `ExportGenesis` invoked on them even if
they weren't supported by the current app version. Now we only call
`ExportGenesis` for the modules that are supported by the current app
version
2. The export command wasn't updated to account for the changes in
celestiaorg/celestia-app#3320 which force us to
mount stores after `app.New()` based on the current app version
3. The minfee module couldn't be exported b/c it didn't register a key
table in `ExportGenesis`

## Testing

I could export an app on app version 1 and 2. See
[output](https://gist.github.com/rootulp/dfea2b5b40f7366b03706fc39321ceee)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant