CONFIRMED by execution. handleTopic (session_commands.go:200) 'off' does setActive(chan, "", getActive(chan, threadID)). With no session cached for (chan, threadID), getActive returns "" and that empty string is stored. resolve treats map presence as authoritative ('id, ok := t.active[key]; if ok { return id }'), and cacheActive also returns the empty existing value, so nothing can repair it.
Reachable when /topic off is the first message on the webhook (webhook.go:169) or email (email.go:207) channel -- both call router.Route directly and never call ResolveSessionKey first, unlike telegram's submitTurn.
Blast radius: every later message in that chat persists under session ID "", history is shared with any other poisoned chat, and the turn-lane key becomes "" so /stop in one chat kills a turn in another.
Same line is also non-atomic: setActive(...getActive(...)) is two critical sections, so a concurrent /resume or /branch is silently clobbered.
Imported from beads archie-core-1786637499318-363-a3050cb6 · GitHub #384 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08
CONFIRMED by execution. handleTopic (session_commands.go:200) 'off' does setActive(chan, "", getActive(chan, threadID)). With no session cached for (chan, threadID), getActive returns "" and that empty string is stored. resolve treats map presence as authoritative ('id, ok := t.active[key]; if ok { return id }'), and cacheActive also returns the empty existing value, so nothing can repair it.
Reachable when /topic off is the first message on the webhook (webhook.go:169) or email (email.go:207) channel -- both call router.Route directly and never call ResolveSessionKey first, unlike telegram's submitTurn.
Blast radius: every later message in that chat persists under session ID "", history is shared with any other poisoned chat, and the turn-lane key becomes "" so /stop in one chat kills a turn in another.
Same line is also non-atomic: setActive(...getActive(...)) is two critical sections, so a concurrent /resume or /branch is silently clobbered.
---
_Imported from beads `archie-core-1786637499318-363-a3050cb6` · GitHub #384 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumbug labels 2026-10-27 13:38:11 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
CONFIRMED by execution. handleTopic (session_commands.go:200) 'off' does setActive(chan, "", getActive(chan, threadID)). With no session cached for (chan, threadID), getActive returns "" and that empty string is stored. resolve treats map presence as authoritative ('id, ok := t.active[key]; if ok { return id }'), and cacheActive also returns the empty existing value, so nothing can repair it.
Reachable when /topic off is the first message on the webhook (webhook.go:169) or email (email.go:207) channel -- both call router.Route directly and never call ResolveSessionKey first, unlike telegram's submitTurn.
Blast radius: every later message in that chat persists under session ID "", history is shared with any other poisoned chat, and the turn-lane key becomes "" so /stop in one chat kills a turn in another.
Same line is also non-atomic: setActive(...getActive(...)) is two critical sections, so a concurrent /resume or /branch is silently clobbered.
Imported from beads
archie-core-1786637499318-363-a3050cb6· GitHub #384 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08