Skip to content

Cover SVN watcher recovery and lifecycle transitions #1122

Open
Open
Cover SVN watcher recovery and lifecycle transitions#1122
Labels
editor/integrationEditor compatibility and CLI integrationenhancementNew feature or requestpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.stability/performanceServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UX
Milestone
0.11.0-rc

Description

@lzl51230
lzl51230
opened on Jul 16, 2026

Scope

Add deterministic watcher-level tests for the recovery and lifecycle branches introduced by #1113. Current tests cover baseline/dedup, callback return retries, and inherited-parent Git precedence.

Coverage

  • Edit during callback and staged-observation acknowledgement.
  • Missing client and malformed/nonzero status recovery.
  • Failed root-Git probe retains Git-first precedence.
  • Definitive non-working-copy settlement.
  • File-count interval refresh and completion-relative SVN scheduling.
  • Replacement/unwatch during active polling and callback.
  • Shutdown and missing-root pruning for SVN registrations.

Activity

  1. github-actions
    added
    ux/behaviorDisplay bugs, docs, adoption UX
    on Jul 16, 2026
  2. DeusData
    added
    enhancementNew feature or request
    taskUmbrella task grouping multiple related issues
    editor/integrationEditor compatibility and CLI integration
    on Jul 16, 2026
  3. DeusData
    added this to the 0.9.2-rc milestone on Jul 16, 2026
  4. DeusData
    added
    stability/performanceServer crashes, OOM, hangs, high CPU/memory
    priority/normalStandard review queue; useful PR with ordinary maintainer urgency.
    on Jul 16, 2026

  5. DeusData commented on Jul 16, 2026

    @DeusData
    DeusData
    on Jul 16, 2026
    Owner

    Tracked as 0.9.2-rc lifecycle coverage for #1113/#1127. Replacement/unwatch during an active callback, failed-client recovery, acknowledgement after success, and shutdown pruning are core correctness paths and should be deterministic before the watcher feature is considered stable. Timing-only sleeps are not sufficient guards for these races.

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

    editor/integrationEditor compatibility and CLI integrationenhancementNew feature or requestpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.stability/performanceServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UX

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions