-
Notifications
You must be signed in to change notification settings - Fork 329
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
Duplicate packets on start #2093
Comments
This is consistent with what we noticed yesterday in the GH action logs --
|
Neither @adizere or I were able to reproduce this issue locally. It's hard to say whether this issue is only exhibited on a particular version of Hermes and/or Gaia, but we both tried with Hermes versions 0.14 and 0.15, as well as Gaia v7, to no avail. We also attempted to reproduce the error using the CI commands that yielded the logs that Adi posted above, but that also bore no fruit. @ancazamfir are you able to reproduce this again and/or provide additional hints/context so that we can reproduce it on our ends? |
Here are the steps I used just now (on master with latest eae0afd):
It doesn't happen all the time, you need to repeat steps 3. and 4. Here are the hermes logs:
|
What does the |
I removed it from the instructions but in general I use the One more comment on the repro, you might have more luck with flipping steps 3 and 4, that is send the packet and immediately start the relayer (before you even see the ft-transfer CLI confirmation). |
Summary of Bug
When a packet worker is started (triggered by an IBC event) it will submit duplicate transaction triggered by clearing on start. I think we need to use
height.decrement()
here:https://github.com/informalsystems/ibc-rs/blob/184a811564d7d699ceb72ad1563f7746a8b98a39/relayer/src/worker/packet.rs#L171
Version
master
Steps to Reproduce
hermes create channel
hermes start
hermes tx raw ft-transfer ibc-1 ibc-0 transfer channel-0 10 -n 1 -o 30 -k user2
MsgRecvPacket
andMsgAcknowledgement
:Acceptance Criteria
Should not submit duplicate transactions
For Admin Use
The text was updated successfully, but these errors were encountered: