Same bad premise as the escape hatch fix in PR #133, bigger blast radius: '''incident_correlator.py''''''s fast/thin correlation path (~line 1005-1007) branches on _is_dispatch_channel to pick tg_dispatch_thin_idle_minutes (5 min) vs tg_thin_idle_minutes (15 min) for which candidate incidents a thin call is eligible to attach to -- an actual LINK decision, not just a gate escape hatch.
Owner correction (2026-09-13, direct scanning experience): a talkgroup named tac/tactical only sees materially different traffic during a real incident, and that is rare -- the bulk of traffic on any monitored channel, including high-risk stops and pursuits, runs on the main channel regardless of what it is named. _is_dispatch_channel is a string match on the configured talkgroup name, not a detector of actual channel behavior.
Unlike the escape hatch (PR #133, low-risk, only changes when a gate stands down), this path directly decides which calls link to which incidents for every thin/no-fit-signal call on every channel not literally named dispatch/patched/primary. Changing it changes correlation decisions, not just measurement -- needs its own scoped review and a measurement window, not a quick fix. Relates to #115.
Same bad premise as the escape hatch fix in PR #133, bigger blast radius: '''incident_correlator.py''''''s fast/thin correlation path (~line 1005-1007) branches on _is_dispatch_channel to pick tg_dispatch_thin_idle_minutes (5 min) vs tg_thin_idle_minutes (15 min) for which candidate incidents a thin call is eligible to attach to -- an actual LINK decision, not just a gate escape hatch.
Owner correction (2026-09-13, direct scanning experience): a talkgroup named tac/tactical only sees materially different traffic during a real incident, and that is rare -- the bulk of traffic on any monitored channel, including high-risk stops and pursuits, runs on the main channel regardless of what it is named. _is_dispatch_channel is a string match on the configured talkgroup name, not a detector of actual channel behavior.
Unlike the escape hatch (PR #133, low-risk, only changes when a gate stands down), this path directly decides which calls link to which incidents for every thin/no-fit-signal call on every channel not literally named dispatch/patched/primary. Changing it changes correlation decisions, not just measurement -- needs its own scoped review and a measurement window, not a quick fix. Relates to #115.
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.
Same bad premise as the escape hatch fix in PR #133, bigger blast radius: '''incident_correlator.py''''''s fast/thin correlation path (~line 1005-1007) branches on _is_dispatch_channel to pick tg_dispatch_thin_idle_minutes (5 min) vs tg_thin_idle_minutes (15 min) for which candidate incidents a thin call is eligible to attach to -- an actual LINK decision, not just a gate escape hatch.
Owner correction (2026-09-13, direct scanning experience): a talkgroup named tac/tactical only sees materially different traffic during a real incident, and that is rare -- the bulk of traffic on any monitored channel, including high-risk stops and pursuits, runs on the main channel regardless of what it is named. _is_dispatch_channel is a string match on the configured talkgroup name, not a detector of actual channel behavior.
Unlike the escape hatch (PR #133, low-risk, only changes when a gate stands down), this path directly decides which calls link to which incidents for every thin/no-fit-signal call on every channel not literally named dispatch/patched/primary. Changing it changes correlation decisions, not just measurement -- needs its own scoped review and a measurement window, not a quick fix. Relates to #115.