search

matrix-org / libera-chat

Support requests for the libera.chat IRC bridge hosted by matrix.org
7 stars 2 forks source link

Some CTCP VERSION requests are not answered #10

Open progval opened 1 year ago

progval commented 1 year ago

This seems to happen when the request is the first in a while:

11:40:37 -- CTCP query to val[m]: VERSION
11:41:17 -- CTCP query to val[m]: VERSION
11:41:17 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:22 -- CTCP query to val[m]: VERSION
11:41:23 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:25 -- CTCP query to val[m]: VERSION
11:41:25 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:37 -- CTCP query to val[m]: VERSION
11:41:37 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:40 -- CTCP query to val[m]: VERSION
11:41:40 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:43 -- CTCP query to val[m]: VERSION
11:41:43 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:45 -- CTCP query to val[m]: VERSION
11:41:45 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:47 -- CTCP query to val[m]: VERSION
11:41:49 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:55 -- CTCP query to val[m]: VERSION
11:41:55 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:41:58 -- CTCP query to val[m]: VERSION
11:41:58 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:42:02 -- CTCP query to val[m]: VERSION
11:42:02 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:42:12 -- CTCP query to val[m]: VERSION
11:42:13 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:42:20 -- CTCP query to val[m]: VERSION
11:42:20 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:42:38 -- CTCP query to val[m]: VERSION
11:42:39 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
11:43:15 -- CTCP query to val[m]: VERSION
11:43:15 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
12:20:08 -- CTCP query to val[m]: VERSION
12:20:09 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
12:20:19 -- CTCP query to val[m]: VERSION
12:20:20 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
12:20:29 -- CTCP query to val[m]: VERSION
12:20:29 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
14:42:12 -- CTCP query to val[m]: VERSION
14:42:26 -- CTCP query to val[m]: VERSION
14:42:27 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat
14:42:32 -- CTCP query to val[m]: VERSION
14:42:33 -- CTCP reply from val[m]: VERSION matrix-appservice-irc 0.38.0 bridged via libera.chat

(timestamps are today, and in UTC)

while this isn't a big deal in itself, this seems to indicate messages are being dropped somewhere between the TCP socket to Libera and the appservice process, and isn't a bridging issue.