You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've already bumped cosmos-sdk to v0.42.9: 8b8c0c6.
Based on it, we should release the v2.0.2 for IBC.
I've tested the IBC transfer with the Gaia localnet v5.0.5, but the following error occurred.
That error was already reported as cosmos/cosmos-sdk#9800 and was fixed at the cosmos-sdk v0.42.9.
I also tested that the IBC channel is created well with the Panacea based on the cosmos-sdk v0.42.9.
~ ❯❯❯ rly tx link transfer tags/v2.0.1 ✭
I[2021-09-03|14:50:57.866] ✔ [testing]@{3185} - msg(0:create_client) hash(71DE75203FA458F4985A1F925705E859D615BC76312F9E9C62245B5C828D81CF)
I[2021-09-03|14:50:59.505] ✔ [gaia]@{312} - msg(0:create_client) hash(66007BD15336B68C0CAC66834B83CBF87E85417A759C350B728C7C0AD9598B20)
I[2021-09-03|14:50:59.505] ★ Clients created: client(07-tendermint-0) on chain[testing] and client(07-tendermint-0) on chain[gaia]
I[2021-09-03|14:51:02.892] ✔ [testing]@{3186} - msg(0:update_client,1:connection_open_init) hash(D836C180798838365D041723470B6CD84D6A1902CA4F280890DC81A8ACF95C4E)
I[2021-09-03|14:51:14.629] ✔ [gaia]@{315} - msg(0:update_client,1:connection_open_try) hash(3459A0969ACA673BFCB1C54B6687B321B92CC8468975B3E5DFD10C99D9FABE54)
I[2021-09-03|14:51:33.179] ✔ [testing]@{3192} - msg(0:update_client,1:connection_open_ack) hash(D280C841B22EFF2CD556399B5DBD1A3A76AAD786F0885E7B0FDADA73B4028979)
I[2021-09-03|14:51:39.806] ✔ [gaia]@{320} - msg(0:update_client,1:connection_open_confirm) hash(F08AD4544B3B4347AC44217F7C1C25CB72E1477A312F85C9295F17284854295B)
I[2021-09-03|14:51:39.806] ★ Connection created: [testing]client{07-tendermint-0}conn{connection-0} -> [gaia]client{07-tendermint-0}conn{connection-0}
I[2021-09-03|14:51:43.240] ✘ [testing]@{3194} - msg(0:update_client,1:channel_open_init) err(port:4:failed to execute message; message index: 1: channel handshake open init failed: caller does not own port capability for port ID transfer: invalid port)
I[2021-09-03|14:51:43.240] retrying transaction...
I[2021-09-03|14:51:49.942] rpc error: code = InvalidArgument desc = failed to execute message; message index: 1: channel handshake open init failed: caller does not own port capability for port ID transfer: invalid port: invalid request
I[2021-09-03|14:51:49.942] retrying transaction...
I[2021-09-03|14:51:59.941] rpc error: code = InvalidArgument desc = failed to execute message; message index: 1: channel handshake open init failed: caller does not own port capability for port ID transfer: invalid port: invalid request
I[2021-09-03|14:51:59.941] retrying transaction...
I[2021-09-03|14:52:09.941] rpc error: code = InvalidArgument desc = failed to execute message; message index: 1: channel handshake open init failed: caller does not own port capability for port ID transfer: invalid port: invalid request
I[2021-09-03|14:52:09.941] retrying transaction...
Error: ! Channel failed: [testing]chan{}port{transfer} -> [gaia]chan{}port{transfer}
One thing we should keep in mind is implementing the upgrade handler which is needed for the SoftwareUpgradeProposal.
That is, we have to take a look at the detail of SoftwareUpgradeProposal and cosmovisor deeply, before releasing the Panacea v2.0.2.
I don't think we should use the cosmos-sdk v0.44 because it contains a lot of breaking changes and it's not stable yet, I guess. It should be upgraded when we release the Panacea v3.
The text was updated successfully, but these errors were encountered:
We've already bumped cosmos-sdk to v0.42.9: 8b8c0c6.
Based on it, we should release the v2.0.2 for IBC.
I've tested the IBC transfer with the Gaia localnet v5.0.5, but the following error occurred.
That error was already reported as cosmos/cosmos-sdk#9800 and was fixed at the cosmos-sdk v0.42.9.
I also tested that the IBC channel is created well with the Panacea based on the cosmos-sdk v0.42.9.
One thing we should keep in mind is implementing the upgrade handler which is needed for the SoftwareUpgradeProposal.
That is, we have to take a look at the detail of SoftwareUpgradeProposal and cosmovisor deeply, before releasing the Panacea v2.0.2.
I don't think we should use the cosmos-sdk v0.44 because it contains a lot of breaking changes and it's not stable yet, I guess. It should be upgraded when we release the Panacea v3.
The text was updated successfully, but these errors were encountered: