App currently throws a runtime error when attempting to decode any IBC Client updates and this should be fixed.
Description
As of now, any Transaction that contains IBC Client updates cannot be decoded by current protobuf schema handling. This is because of an internal Any schema decoding error that inevitably gets thrown by the TxResult decoder. This has occurred with anything containing an internalMsgCreateClient protobuf schema (e.g. create_client ABCI events) but occurs with other IBC Client related transactions.
This can probably be fixed by one of the following:
simply update the protobuf schemas. this might already be resolved by penumbra's core team and their recent work with IBC.
the recently released NPM packages by the web team which has converged on a set of patterns with dealing with this sort of data
monkey patching the schema directly so as to handle instances where Any are encountered
ejmg
commented
3 weeks ago
Summary
App currently throws a runtime error when attempting to decode any IBC Client updates and this should be fixed.
Description
As of now, any Transaction that contains IBC Client updates cannot be decoded by current protobuf schema handling. This is because of an internal
Anyschema decoding error that inevitably gets thrown by theTxResultdecoder. This has occurred with anything containing an internalMsgCreateClientprotobuf schema (e.g.create_clientABCI events) but occurs with other IBC Client related transactions.This can probably be fixed by one of the following:
Anyare encountered