Inspector shows Slack inbox rows after switching to GitHub
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start from the Settings → Sync view that renders the /settings/sync/github route and follow how the Slack and GitHub inbox rows are fetched and stored; the bug is a late response from the Slack request overwriting the row for the tab that is now selected. Reproduce by delaying the Slack inbox response as described, then look for where the finished request writes its result without checking which tab is active (or without cancelling the previous request). Done means switching tabs mid-load leaves the newly selected tab's row in place, with no stale Slack data appearing.
Written by the indexing model from the issue text.
Description
Checking the sync inboxes in Inspector and noticed that GitHub can finish loading, then switch back to showing Slack’s rows while the GitHub tab is still selected.
- Open Settings → Sync → Slack.
- Click GitHub while Slack is still loading. The GitHub row appears.
- When the Slack request finishes, its row replaces the GitHub row. The URL still says
/settings/sync/github.
I’d expect the GitHub row to stay there. Clicking Refresh brings it back.
Reproduced on @vercel/board 0.54.0 (86694bd) in Chromium. For the recording, I delayed the Slack inbox response by five seconds so I could switch to GitHub while it was still loading.
https://github.com/user-attachments/assets/19a31277-5a55-489c-891e-631f8dea80ef
- Dominant language
- TypeScript
- Stars
- 178
- Forks
- 16
- Avg merge
- 8h 44m
- Merged PRs (30d)
- 411
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/board
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
T3 Code mappingOpen
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
kind:defect
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mux-labs/mux-frontend#1240 ·
Maintainers usually reply within 1 day
-
area: agents-mcp priority: normal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Wait for the IDS correction dialog to settle in the stale-audit testPossibly taken @louistrue claimed this today. Openready
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Hono path parameters with a regex pattern keep the pattern in the OpenAPI pathPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cloudflare/chanfana#400 ·
Maintainers usually reply within 1 day