-
Notifications
You must be signed in to change notification settings - Fork 92
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
ExportGenesisState
renamed to ExportGenesisHead
in Polkadot-SDK 1.6.0
#1712
Labels
bug
Something isn't working
Comments
Hi @rphmeier, thanks for reporting! I will fix this asap and draft a new release. |
Thanks @pepoviola ! |
Hi @rphmeier, I just release a new version https://github.com/paritytech/zombienet/releases/tag/v1.3.92 that includes this fix. Thanks! |
gabriele-0201
added a commit
to thrumdev/blobs
that referenced
this issue
Feb 9, 2024
The alias is no longer needed by zombienet after the following issue was solved in version 1.3.92 paritytech/zombienet#1712 (comment)
rphmeier
pushed a commit
to thrumdev/blobs
that referenced
this issue
Feb 9, 2024
The alias is no longer needed by zombienet after the following issue was solved in version 1.3.92 paritytech/zombienet#1712 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
ZombieNet still uses
ExportGenesisState
and should be able to handle nodes which only have anExportGenesisHead
command.At the moment, chains build using Polkadot-SDK 1.6.0 cannot use ZombieNet without continuing to expose an
ExportGenesisState
command.Steps to reproduce the issue
run ZombieNet with a chain built using Polkadot-SDK 1.6.0 which does have
ExportGenesisHead
and does not haveExportGenesisState
.Describe the results you received
n/a
Describe the results you expected
n/a
Zombienet version
1.3.91
Provider
Native
Provider version
N/A
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Screenshots
No response
The text was updated successfully, but these errors were encountered: