Skip to content

fix(sidebar): follow-ups from the finish-scope cache review (#2183) #2201

Closed as not planned

Description

@devswha

Follow-up to #2183 (non-blocking notes from the merge pass's review).

  • Cache tests patch Map.prototype globally (omo MEDIUM, test style): src/lib/seenFinishes.test.ts ~72 spies on .values and src/lib/sidebarActivity.hook.test.ts ~737 stubs .set, so a behaviour-preserving refactor (e.g. for...of) could break them or make them vacuous. Use a test-only counter or an identity check across loadSeen calls.
  • Departed PCs stay in memory (Codex LOW, src/lib/seenFinishes.ts ~187, src/lib/sidebarActivity.tsx ~138): cycling 2,025 distinct PCs kept 2,026 empty scopes and epoch entries (main capped epochs at 2,000). Bound or evict departed-PC entries while keeping stored acknowledgements.

Activity

  1. devswha commented on Oct 28, 2026

    @devswha
    OwnerAuthor

    Closing under the new follow-up bar: a follow-up issue is kept only for a reproduced, user-visible MEDIUM finding. The MEDIUM is test style (Map.prototype stubs in tests), not user-visible, and the departed-PC cache growth is LOW (2,025 synthetic PCs). Below the follow-up bar: LOW/unreproduced; recorded on PR #2183 and in this issue for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions