disinto-admin/disinto

Fork 0

fix: dispatcher uses old single-label names instead of bug-report combo labels #339

New issue

Closed

opened 2026-04-07 08:16:42 +00:00 by dev-bot · 1 comment

dev-bot commented

2026-04-07 08:16:42 +00:00

Collaborator

Problem

The dispatcher in docker/edge/dispatcher.sh still checks for the old single-purpose labels:

needs-triage (old) → should be bug-report + in-triage (new)
reproduced, cannot-reproduce in the skip set → should be in-progress, rejected

The reproduce-agent (#320) now applies combo labels (bug-report + in-triage, bug-report + rejected, etc.) but the dispatcher skip filter still looks for the old names. This means:

Dispatcher will not skip already-processed issues (keeps re-dispatching)
Triage dispatch (#258) will never trigger (looks for needs-triage which is never applied)

Fix

In docker/edge/dispatcher.sh, fetch_reproduce_candidates():

# Old:
skip = {"reproduced", "cannot-reproduce", "needs-triage"}
# New:
skip = {"in-progress", "in-triage", "rejected", "blocked"}

And the triage dispatch (when #258 lands) should trigger on in-triage label, not needs-triage.

Files

docker/edge/dispatcher.sh — fetch_reproduce_candidates() skip set, and future triage dispatch trigger

## Problem The dispatcher in `docker/edge/dispatcher.sh` still checks for the old single-purpose labels: - `needs-triage` (old) → should be `bug-report` + `in-triage` (new) - `reproduced`, `cannot-reproduce` in the skip set → should be `in-progress`, `rejected` The reproduce-agent (#320) now applies combo labels (`bug-report` + `in-triage`, `bug-report` + `rejected`, etc.) but the dispatcher skip filter still looks for the old names. This means: - Dispatcher will not skip already-processed issues (keeps re-dispatching) - Triage dispatch (#258) will never trigger (looks for `needs-triage` which is never applied) ## Fix In `docker/edge/dispatcher.sh`, `fetch_reproduce_candidates()`: ```python # Old: skip = {"reproduced", "cannot-reproduce", "needs-triage"} # New: skip = {"in-progress", "in-triage", "rejected", "blocked"} ``` And the triage dispatch (when #258 lands) should trigger on `in-triage` label, not `needs-triage`. ## Files - `docker/edge/dispatcher.sh` — `fetch_reproduce_candidates()` skip set, and future triage dispatch trigger

dev-bot added the

backlog

label 2026-04-07 08:16:42 +00:00

dev-bot self-assigned this 2026-04-07 08:34:03 +00:00

dev-bot added

in-progress

and removed

backlog

labels 2026-04-07 08:34:03 +00:00

dev-qwen added

blocked

and removed

in-progress

labels 2026-04-07 08:34:13 +00:00

dev-qwen commented

2026-04-07 08:34:13 +00:00

Collaborator

Stale in-progress issue detected

Field	Value
Detection reason	`no_active_session_no_open_pr`
Timestamp	`2026-04-07T08:34:13Z`

Status: This issue was labeled in-progress but no active tmux session exists.
Action required: A maintainer should triage this issue.

### Stale in-progress issue detected | Field | Value | |---|---| | Detection reason | `no_active_session_no_open_pr` | | Timestamp | `2026-04-07T08:34:13Z` | **Status:** This issue was labeled `in-progress` but no active tmux session exists. **Action required:** A maintainer should triage this issue.

dev-bot referenced this issue from a commit

2026-04-07 08:34:44 +00:00

fix: fix: dispatcher uses old single-label names instead of bug-report combo labels (#339)

dev-bot referenced this issue from a pull request that will close it,

2026-04-07 08:34:47 +00:00

fix: fix: dispatcher uses old single-label names instead of bug-report combo labels (#339) #345

dev-bot closed this issue

2026-04-07 08:39:02 +00:00

dev-bot removed their assignment 2026-04-07 08:39:03 +00:00

dev-bot referenced this issue from a commit

2026-04-07 08:39:03 +00:00

Merge pull request 'fix: fix: dispatcher uses old single-label names instead of bug-report combo labels (#339)' (#345) from fix/issue-339 into main