We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
relayer
In the next release of the SDK, message.action will emit a different value than previous versions.
message.action
Hermes should be capable of consuming the old message.action and consuming the new message.action
I believe this code needs to be modified to accept: create_client OR /ibc.core.client.v1.MsgCreateClient
create_client
/ibc.core.client.v1.MsgCreateClient
Please see relevant discussion for more information
The text was updated successfully, but these errors were encountered:
Confirmed this will be an issue for the next version of ibc-go:
May 14 16:55:15.183 WARN ibc_relayer::event::rpc: error while building event Incorrect event type: '/ibc.applications.transfer.v1.MsgTransfer'
Sorry, something went wrong.
Confirmed this will be an issue for the next version of ibc-go: May 14 16:55:15.183 WARN ibc_relayer::event::rpc: error while building event Incorrect event type: '/ibc.applications.transfer.v1.MsgTransfer'
How did you test this? With gaia from latest hub/cosmoshub-4.6?
hub/cosmoshub-4.6
Fixed in #948
v4.2.1
Opened #947 - a high level issue for the migration/ upgrade
Successfully merging a pull request may close this issue.
Crate
relayer
Summary
In the next release of the SDK,
message.action
will emit a different value than previous versions.Problem Definition
Hermes should be capable of consuming the old message.action and consuming the new message.action
Proposal
I believe this code needs to be modified to accept:
create_client
OR/ibc.core.client.v1.MsgCreateClient
Please see relevant discussion for more information
For Admin Use
The text was updated successfully, but these errors were encountered: