dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.3.1 | You're being logged at https://irclog.whitequark.org/cinch/
kith has quit [Quit: kith]
_whitelogger has joined #cinch
whitequark has joined #cinch
<whitequark> dominikh: so... just discovered an issue in irclogger, after all these years
<dominikh> oh?
<whitequark> if several messages in the same channel from the same user arrive in rapid succession, there's a race
<whitequark> (at least, as far as I understand)
<dominikh> are you using matchers and/or listeners for this?
<whitequark> listen_to, so listeners, I think
<dominikh> then yeah, that'll race.
<dominikh> if you want something that won't race, you'd need to implement a Logger
<whitequark> this doesn't seem related
<whitequark> should I use #incoming?
<dominikh> you would write a Logger with an implementation of #incoming that parses the message and acts appropriately when it's a PRIVMSG in a channel you're tracking.
<dominikh> completely alternatively:
<dominikh> messages have timestamps. can your data store do out of order insertions?
<whitequark> oh, are messages timestamped *before* spawning a thread?
<dominikh> yes
<whitequark> that would also fix it
<whitequark> thanks
<dominikh> it's set right after parsing
whitequark has left #cinch [#cinch]