Repository navigation
Description
Operating system
macOS client connected to a Windows 11 Orca server.
Orca version
v1.4.135 on both hosts.
Details
Short summary
A newly paired Windows runtime can appear in the macOS All hosts sidebar for a few seconds and then lose its host section even though the runtime remains connected and continues returning the same repositories and worktrees. When Smart ordering is active, the macOS renderer can also enter a repeated sort-order persistence/refresh cycle and consume more than one CPU core.
This report is intentionally sanitized: network addresses, usernames, hostnames, repository paths/names, runtime/device IDs, and screenshots have been omitted.
Reproduction
- Run Orca on a macOS client and a Windows 11 server using the same release.
- Pair the Windows server from the macOS sidebar.
- Keep All hosts and Smart workspace ordering enabled, with at least one live terminal session.
- Observe that the Windows host section initially appears with its workspaces, then can disappear or be regrouped under the local host.
- Observe repeated remote catalog refreshes and sustained renderer CPU usage.
Expected
- A reachable registered host remains represented by its own workspace rows.
- Concurrent local and runtime catalog refreshes preserve rows owned by the other host.
- Persisting an unchanged Smart order does not trigger an endless refresh/persist cycle.
Actual
- The runtime stays registered and reachable; authenticated RPCs continue succeeding.
- Repeated
repo.listcalls return the same non-empty catalog, andworktree.listremains stable. - The client/server WebSocket remains established.
- The Windows profile's
sortOrdervalues are rewritten approximately every 3–5 seconds while the macOS renderer remains busy.
Root-cause evidence
Two related paths are involved:
- In v1.4.135,
fetchRepos()andfetchRuntimeEnvironmentRepos()both merge a fetched host catalog againstget().reposcaptured before theirawait, then replace the fullreposarray. A late local fetch can therefore overwrite runtime rows that a faster runtime fetch just added. A deterministic store-level reproduction produces[remote]after the runtime fetch and[local]after the late local fetch. - Smart ordering persists every newly allocated
sortedIdsarray to the owner host. The runtime rewrites eachsortOrderwithDate.now()and emitsreposChanged; the client refreshes repos/worktrees, treats the newsortOrderas a worktree change, incrementssortEpoch, recomputessortedIdsafter the settle delay, and persists again.
Current main already merges fetched repo catalogs inside set(state) against the latest state.repos as part of 25ecf2eea, which structurally addresses the stale catalog overwrite. It does not currently have a regression test for the local-vs-runtime overlap, and the unchanged-order Smart persistence loop remains.
Acceptance criteria
- Add a regression test where a runtime catalog resolves before an older local catalog and both hosts remain in state.
- Make repeated persistence of the same per-host workspace order a no-op and avoid emitting another broad refresh event.
- Preserve persistence and notification when the effective order actually changes.
- Cover macOS-client/Windows-server behavior without platform-specific path assumptions.
Activity
OrcaWin commentedon Jul 17, 2026
Agent reproduction package (Windows orchestration 2026-07-16)
Host context: Windows 11 / Orca 1.4.143.0 / repo path used:
docs/bug-reproductions/Labels applied: see issue labels (
has_reproorcannot_repro).Security: Do not run user-uploaded binaries from issue attachments. Recreate fixtures from the steps/scripts below.
Issue 8272 — Remote Windows host disappears during smart sort
Status:
needs_setupHost: Windows 11 only (no macOS client)
Label: none
Summary
Reporter (macOS client ↔ Windows 11 Orca server): newly paired Windows host appears briefly under All hosts, then host section vanishes / regroups under local host while Smart ordering is on; renderer CPU high;
sortOrderrewritten every 3–5s.Environment gates (this host)
Source notes (main)
Reporter already identified:
fetchReposoverwriting runtime rows (addressed structurally by merging insideset(state)/mergeFetchedRepoCatalog— seesrc/renderer/src/store/slices/repos.ts, tests underrepos-all-hosts*.ts,repos-stale-fetch.test.ts)Date.now(), emitting refresh cyclesRenderer unit tests that would cover (1) failed to load in this environment (
Cannot find package '@/i18n/i18n'when running vitest on those files without full web config) — not a product cannot_repro.Repro needs (another agent)
Evidence
docs/bug-reproductions/issues/8272.jsonorca environment listempty on this hostrepos.tsmergeFetchedRepoCatalog/fetchRuntimeEnvironmentReposWhy blocked
Requires dual-machine macOS↔Windows pairing topology; this host is Windows-only with no remote environments.
How another agent should use this
%LOCALAPPDATA%\Programs\orca).--json, screenshots, logs) under a local folder; optionally comment results back here.cannot_repro/ needs_setup, satisfy the listed prerequisites first, then re-attempt and flip labels: removecannot_repro, addhas_reprowhen conclusive.nwparker commentedon Aug 31, 2026
Resolved by merged PR #13662 (commit 84bd306), which avoids no-op worktree sort writes and prevents the disappearing-host refresh loop. Closing as completed.