Commit Graph
3 Commits
Author SHA1 Message Date
NeilandOrca aab112933e Revert "fix(memory): bound OOM-prone accumulators (#10179)" (#10255)
Co-authored-by: Orca <help@stably.ai>
2026-07-23 18:35:31 -07:00
Neil 8f40ddf328 fix(memory): bound OOM-prone accumulators (#10179) 2026-07-23 06:22:56 -07:00
b259300032 perf(worktrees): bound runtime discovery scans (#8915)
* perf(worktrees): bound repeated runtime discovery scans (#8882)

* fix(worktrees): invalidate scans on SSH state changes (#8882)

* fix(worktrees): key scan reuse by execution runtime (#8882)

* test(worktrees): prove cached lineage variants (#8882)

* test(worktrees): exercise lineage through the shared scan cache (#8882)

* fix(worktrees): prevent stale runtime scans from repopulating cache (#8882)

* test(worktrees): prove stale generations stay out of cache (#8882)

* fix(worktrees): invalidate hidden SSH scans on relay state (#8882)

* fix(worktrees): scope SSH scan invalidation to provider changes (#8882)

* fix(worktrees): preserve enriched hidden SSH state notifications (#8882)

* test(worktrees): pin SSH provider generation monotonicity (#8882)

* test(worktrees): drain cached scan mock responses (#8882)

* fix(worktrees): scope resolved SSH invalidation to affected repos (#8882)

* fix(worktrees): separate SSH scan invalidation from client events (#8882)

* perf(worktrees): preserve raw scan reuse across metadata updates

# Conflicts:
#	src/main/runtime/orca-runtime.ts

* perf(worktrees): scope repo-local scan invalidation

# Conflicts:
#	src/main/runtime/orca-runtime.ts

* perf(worktrees): scope all repository scan invalidations

* fix(worktrees): drop scan cache on orphan-cleanup removal (#8882)

The orphan-cleanup fallback in removeManagedWorktree (git worktree remove
fails with 'not a working tree', Orca deletes the directory and prunes)
invalidated only the resolved cache, so the removed worktree kept being
served from the bounded raw scan cache for up to its 30s TTL.

Co-authored-by: Orca <help@stably.ai>

* Simplify SSH deploy-success handling to use broadcastSshState

Route the post-deploy "connected" notification through the shared
broadcastSshState helper instead of manually reimplementing window
broadcast and runtime cache invalidation inline, keeping SSH state
propagation consistent with other call sites.

* perf(worktrees): defer SSH enrichment, consolidate cache invalidation

- Skip enriching ephemeral-VM SSH state since it's not broadcast to the
  renderer, avoiding unnecessary withSshRemotePlatform() calls.
- Move invalidateResolvedWorktreeCache() outside the conditional branch
  to eliminate redundant calls (previously called in both if and else).

---------

Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Co-authored-by: Orca <help@stably.ai>
2026-07-17 15:34:30 -07:00