Closed adizere closed 1 year ago
Working on this is blocked on an available node that has the packet data for the stuck packet. Right now, we're using a Notional archive node and working in tandem with Jacob to debug.
cleared with hermes 1.1.0 and a whole lot of gas
@doggystylez Sweet! Did it just go through with clear packets
or were there additional steps to be taken?
Way to go @doggystylez!
We'll coordinate with the IBC-go team & SDK to see where's the best place for implementing preventive measures. A proof-of-concept solution for preventing these kind of corner-cases in the future exists here: https://github.com/cosmos/ibc-go/pull/2983.
@romac clear packets
worked
what I did:
rpc
endpoint (not being proxied)grpc
endpointI noted that the osmosis app.toml has a setting for grpc max-recv-msg-size
(which conveniently defaults to 10MB in the latest version), going to check this out further
Summary of Bug
@faddat discovered this
SendPacket
stuck last week.Receiver
field is hugeVersion
v1.2
Steps to Reproduce
clear packets
, Hermes is not able to pull the packet data for this packet.The main part is
serde parse error: EOF while parsing a string at line 188 column 524468
.tx packet-recv
(instead ofclear packets
) gets Hermes more progressThe main part here is HTTP error 413, likely because of nginx frontend to Notional RPC nodes.
Acceptance Criteria
1,275,507
relayedFor Admin Use