I've just built senpai from 14f45e04057d9c17085c1fbdd3080ad98d267199 using go 1.23.4 (on Fedora 41). I'm connected to soju built from 1f8f8520f0526dfb9814fae7b5cb7251d5ce4710. Periodically, senpai is crashing with the message:
panic: cannot found session "2" for message ":48c094e6f771 CAP * LS :echo-message draft/read-marker setname draft/chathistory soju.im/search extended-monitor account-tag draft/pre-away soju.im/bouncer-networks-notify invite-notify soju.im/webpush soju.im/account-required message-tags cap-notify draft/no-implicit-names chghost extended-join draft/metadata-2=before-connect,max-keys=0,max-value-bytes=1 soju.im/read soju.im/no-implicit-names soju.im/bouncer-networks sasl=PLAIN away-notify server-time draft/extended-monitor multi-prefix batch account-notify"
goroutine 1 [running]: git.sr.ht/~delthas/senpai.(*App).handleIRCEvent(0xc0000e6248, {0xc000644310, 0x1}, {0x824e40?, 0xc0007ee2c0?}) /home/lars/src/senpai/app.go:1252 +0x6939 git.sr.ht/~delthas/senpai.(*App).handleEvent(0xc0000419e0?, {{0xc000644310?, 0x0?}, {0x824e40?, 0xc0007ee2c0?}}) /home/lars/src/senpai/app.go:336 +0x54 git.sr.ht/~delthas/senpai.(*App).eventLoop(0xc0000e6248) /home/lars/src/senpai/app.go:278 +0x6e8 git.sr.ht/~delthas/senpai.(*App).Run(0xc0000e6248) /home/lars/src/senpai/app.go:241 +0x125 main.main() /home/lars/src/senpai/cmd/senpai/main.go:200 +0xa05
I have configured soju with connections to libera and oftc.
Hi, is this perhaps a duplicate of https://todo.sr.ht/~delthas/senpai/120 ? ie did this happen when you deleted or edited a bouncer network?
I'm honestly not sure. I'll play with it a bit more this evening and try to trigger it again and pay more attention to what's happening. The traceback seems different from that shown in #120.