A deleted or archived Slack channel leaves its room bound, agents posting into nothing, and no one told
メンテナーはふだん 1 日以内に返信
@Darshan3690 がすでに取り組んでいます。
2026年11月15日 から。
評価
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Python
- スター
- 4.5k
- フォーク
- 348
- 平均マージ
- 1日 17時間
- マージ済み PR(30日)
- 287
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
sandbox-quantum/switch のほかの issue
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskオープン
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
sandbox-quantum/switch#2163 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
sandbox-quantum/switch#2162 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
sandbox-quantum/switch#2159 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
sandbox-quantum/switch#2157 ·
メンテナーはふだん 1 日以内に返信
-
Get-Switch-Console link points at a path that only resolves via a redirect対応中かも @Darshan3690 が 3 日前に担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
sandbox-quantum/switch#1998 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
sandbox-quantum/switch の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
mohanraj00/entelos#200 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 68/100
-
sweep
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
bketelsen/truenas-mcp#77 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
openedx/xblock-lti-consumer#765 ·
メンテナーはふだん 1 日以内に返信
-
bug pydanty:is-working
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
pydantic/pydantic-ai#13939 ·
メンテナーはふだん 1 日以内に返信