A deleted or archived Slack channel leaves its room bound, agents posting into nothing, and no one told
I maintainer di solito rispondono entro 1 giorno
@Darshan3690 ci sta già lavorando.
Dal 15/11/2026.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- Mezza giornata
- Idoneità per principianti
- 45/100
Direzione di ricerca
Start in core/switch_core/bridges/collaboration/slack/adapter.py: dispatch_event falls through with no branch for channel_deleted, channel_archive or channel_unarchive, and send_message swallows SlackApiError after logger.error. The manifest that requests the event subscriptions is also relevant. Done means channel_not_found and is_archived are handled as terminal, with a visible system line posted to the room; the manifest change is optional and larger.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What happens today
Delete (or archive) a Slack channel that a Switch room is bridged to, and Switch does not react at all.
- The event never arrives. The app manifest requests
app_home_opened,message.channels,message.groups,message.imandmessage.mpim.channel_deleted,channel_archiveandchannel_unarchiveare not among them. - It would not be handled if it did.
dispatch_eventincore/switch_core/bridges/collaboration/slack/adapter.pyroutes slash commands, interactive payloads,messageandmember_joined_channel. Anything else falls off the end of the function with no branch and no log. - The room stays bound.
bridge_id,external_channel_idandchannel_typekeep pointing at a channel that no longer exists, and the in-memory map is rebuilt from those rows on every restart. The only code that clears a binding is whole-workspace disconnect. - Agents carry on. An agent's
post_messagesucceeds and persists, because the relay to Slack happens afterwards in a separate consumer.send_messagethen swallows theSlackApiError—logger.error(...)andreturn None— sochannel_not_foundandis_archivedare indistinguishable from a transient failure and from each other. - Nobody is told. No system post in the room, no notice to a workspace admin, no telemetry event. The only durable signal is repeated error lines in the server log.
Archiving behaves identically. If someone later un-archives the channel the bridge silently resumes, because the stale mapping is still intact — accidental rather than designed.
Why this is worth fixing
This is the failure mode CLAUDE.md singles out: "Prefer a visible failure over a silent fallback" and "Never silently swallow errors to keep things 'working.'" A room whose external half has been deleted looks completely healthy from inside Switch. People go on addressing agents, agents go on answering, and none of it reaches anyone.
There is a second-order consequence worth noting separately: messages already mirrored from that channel into Switch are retained indefinitely, since message rows cascade on the room foreign key and the room is never archived or deleted. Deleting a channel in Slack therefore removes the Slack-side copy and nothing else. That may well be the correct product behaviour, but it is currently undocumented and nothing surfaces it.
Suggested direction
Smallest useful change first:
- Distinguish the dead-channel errors from transient ones.
channel_not_foundandis_archivedare terminal; treating them as a generic send failure is what makes this invisible. - Say so in the room. A system line ("this room's Slack channel no longer exists; messages are not reaching it") turns a silent failure into a visible one and needs no new subscription.
- Optionally subscribe to
channel_deleted/channel_archiveto react immediately rather than on the next failed send. This needs a manifest change, so it is the larger step.
Marking the room as unbridged automatically is deliberately not suggested here — that destroys the mapping an un-archive would otherwise restore, and it is a product decision rather than a bug fix.
- Lingua principale
- Python
- Stelle
- 4.5k
- Fork
- 348
- Merge medio
- 1g 17h
- PR unite (30g)
- 287
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di sandbox-quantum/switch
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
sandbox-quantum/switch#2163 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
sandbox-quantum/switch#2162 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
sandbox-quantum/switch#2159 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
sandbox-quantum/switch#2157 ·
I maintainer di solito rispondono entro 1 giorno
-
Get-Switch-Console link points at a path that only resolves via a redirectForse già presa @Darshan3690 l’ha presa 3 giorni fa. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
sandbox-quantum/switch#1998 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di sandbox-quantum/switch
Issue simili
-
bug pydanty:is-working
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
pydantic/pydantic-ai#13939 ·
I maintainer di solito rispondono entro 1 giorno
-
priority: low python
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
LearningCircuit/local-deep-research#8849 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
francescopace/espectre#223 ·
I maintainer di solito rispondono entro 3 giorni
-
good first issue Status: Triaged
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
canonical/imagecraft#538 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
YaShDsOnI/clipwatcher#3 ·