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

Improve errors when publishing a chain with an outdated config.yml #3025

Closed
fadeev opened this issue Oct 31, 2022 · 2 comments · Fixed by #3052
Closed

Improve errors when publishing a chain with an outdated config.yml #3025

fadeev opened this issue Oct 31, 2022 · 2 comments · Fixed by #3052
Assignees

Comments

@fadeev
Copy link
Contributor

fadeev commented Oct 31, 2022

This error doesn't mean much to a normal user.

$ ignite n chain publish github.com/foo/bar
Source code fetched
Blockchain set up
config version v1 is required and the current version is v0
@jeronimoalbi
Copy link
Member

Agreed 👍

This error appears when the existing chain config version is different than the config needed by the Ignite CLI version being run. In this specific case you are running an older binary against a chain with a newer version so the solution is to use a newer binary.

  • The error message definitely needs more context for the user
  • We should add the config version to the CLI version command output
  • We could add a command to migrate the config to the latest version (downgrading doesn't make much sense I think)

Automatic update is not ideal in this case because it would need to be done locally before compiling the app binary and those changes wouldn't be committed.

@jeronimoalbi
Copy link
Member

With the changes from #3052 the output would be:

$ ignite n chain publish github.com/foo/bar
Source code fetched
Blockchain set up
Blockchain init failed: blockchain app uses a previous config version v0 and CLI expects v1
Use a recent CLI version or upgrade blockchain app's config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants