Repository navigation
Cross-seed "Recent Runs" hides the active run when it's on a different instance than the one selected (sometimes, not always) #2132
Replies: 1 comment
Agent BriefCategory: bug Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: The reporter proposes three UI directions — merge the active run into Recent Runs, follow the selector to the running instance, or give the active run its own affordance — and offered a patch for whichever one qui wants. Which one to take is a UI placement call. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
On the Cross-Seed page, the Recent Runs list only includes the in-progress search run when the instance selected in the search selector matches the instance the run is actually executing on. When they differ, the running run is absent from Recent Runs — so you lose the clickable live run and its per-torrent detail — even though the page header still shows RUNNING with live progress. It's easy to hit when running seeded search across more than one instance.
This doesn't typically happen when the scan is started (the new run appears as running initially), but if you navigate away and then go back to that panel on that page, it seems that the current run doesn't show up any longer.
Steps to reproduce
processed/total).Environment
Version: qui v1.22.0, self-hosted single binary, Linux (Debian LXC on Proxmox). Multiple qBittorrent instances configured on docker separate LXC; seeded search (Library scan) run manually across multiple instances.
Relevant logs
Root cause
The header and the list are fed from two decoupled sources (line refs against current
main):Live status header uses
searchStatus.run, which is instance-independent —CrossSeedPage.tsx:1467,:1989.Recent Runs is scoped to the selected
searchInstanceId:searchInstanceIdis a local selection — seeded once from saved search settings / first instance, and thereafter only changed by the selector::865,:1148,:1159,:2539.The list render already handles a running row (spinner +
processed/total), so the row is clearly meant to appear there —:2667,:2671. The only gap is thatlistCrossSeedSearchRunsis filtered to the selected instance while the active run can be on a different one (searchStatus.run.instanceId).The backend is not involved:
ListSearchRunsisWHERE instance_id = ? ORDER BY started_at DESCwith no status/completed_atfilter (internal/models/crossseed.go:1509), so the run is present in its own instance's list — it's just not the list being displayed.Suggested fix (directions — design is your call)
searchStatus.running && searchStatus.run && searchStatus.run.instanceId !== searchInstanceId, prependsearchStatus.runtosearchRunsfor display. Most contained — display-only, no selector side effects.searchStatus.run.instanceId.Happy to put together a patch for whichever direction you prefer — I understand PR creation is collaborators-only, so I can attach a
git diffor link a fork branch here. Wanted to confirm the intended direction first since it's a small UX call.Checklist
All reactions