-
Notifications
You must be signed in to change notification settings - Fork 545
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
v0.43.x Compatibility #1439
Comments
Thanks for reporting! fwiw I'm getting:
|
This doesn't look right. It's using a really old version (v0.1.7). Are you sure you're trying on the |
Yeah, sorry, must've switched back to main. Can reproduce the same issue as you reported. |
This could have nothing to do with cosmos/cosmos-sdk#9827. It could just be general v0.43 support. |
@alexanderbez it is. I think it is very simple, changing a struct. If only I could find the correct struct, I think it is where May touch on this later today. |
This is fixed by #1455. But now starport fails while running the gentx command because it does not follow the standard arguments:
|
Thanks for the fix @ilgooz! Unfortunate about |
Feel free to close this issue once #1455 is merged. When can we expect the next release? |
@ilgooz I've made a gentx command change on |
@alexanderbez hey! Yes, it works after your updates. If you need the fix to be available soon, maybe we can make a dedicated point release for it cc @fadeev. Otherwise, you can expect to see a new release someday next week. |
Yeah, if it's urgent, we can do a point release, otherwise, v0.17.2 next week. |
Not urgent. Thanks @fadeev :) |
Done! |
Describe the bug
Startport fails to start chain on latest v0.43-rc3 SDK release.
To Reproduce
Steps to reproduce the behavior:
$ starport chain serve --reset-once -v -c ./starport.ci.yml
My guess is that it might be related to cosmos/cosmos-sdk#9827. I'm not sure how Starport generates the gentxs, but it could be related to the expected input of
--pubkey
.Please provide output of commands
starport version
go version
uname -a
The text was updated successfully, but these errors were encountered: