Hermes clear_on_start
toggle does not work
#1872
Labels
A: bug
Admin: something isn't working
I: CLI
Internal: related to the relayer's CLI
I: configuration
Internal: related to Hermes configuration
I: logic
Internal: related to the relaying logic
Milestone
Crate
ibc-relayer
andibc-relayer-cli
Summary of Bug
It seems that configuring
clear_on_start = false
does not work. When this is set tofalse
, Hermes should not try to clear packets at startup. But this is not the case. Instead, we're hardcoding that the clearing should always happenhttps://github.com/informalsystems/ibc-rs/blob/aef0e6a92736239d50048e35c73c5eca8c9b7814/relayer/src/link/relay_path.rs#L125
The problem was reported by a relayer operator on Bandchain network. They are probably the only ones using
clear_on_start = false
(I'm not aware of other operators usingfalse
here, and we don't have tests covering this feature, hence this bug went unnoticed for quite some time).Logs folded here, but not sure they are truly useful. The more important part is the "steps to reproduce" described below.
Logs
Version
v0.11.1
Steps to Reproduce
gm
. Suppose the two networks andibc-0
andibc-1
.channel-0
between the two networks.ft-transfer
onchannel-0
ofibc-0
clear_on_start
to befalse
in the config.toml of Hermes.log_level = 'debug'
.clear_interval = 0
to completely disable periodic packet clearing.hermes start
.clear{}
span appearing in the log lines:Under normal circumstances, when
clear_on_start = false
, Hermes should not immediately clear packets upon startup.Acceptance Criteria
clear_on_start
option should translate into the correct Hermes behavior: if set tofalse
, thenhermes start
should proceed to relaying live packets immediately (instead of relaying old packets)For Admin Use
The text was updated successfully, but these errors were encountered: