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
While writing the e2e tests for ics20, I noticed the relayer did not relay my packets before the next assertion came. This issue was solved by adding a .waitForBlocks call. Several blocks were required to be waited on. Instead of waiting for enough blocks to be committed for the relayer to relay the packet, we should wait on the packet to be relayed by. I guess this can be done by waiting for a block to be committed and then querying to see if the packet was relayed, otherwise wait for the next block. Any other ideas?
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged/assigned
The text was updated successfully, but these errors were encountered:
I think we could generalize this one step further and simply have a WaitForCondition(func() (bool, error)). This should be quite flexible and let us wait for arbitrary conditions to be met. We would also need to specify a timeout and some sort of polling interval.
Summary
While writing the e2e tests for ics20, I noticed the relayer did not relay my packets before the next assertion came. This issue was solved by adding a
.waitForBlocks
call. Several blocks were required to be waited on. Instead of waiting for enough blocks to be committed for the relayer to relay the packet, we should wait on the packet to be relayed by. I guess this can be done by waiting for a block to be committed and then querying to see if the packet was relayed, otherwise wait for the next block. Any other ideas?For Admin Use
The text was updated successfully, but these errors were encountered: