Skip to content

fix(tests): reset telemetry singleton to prevent cross-test fetch leakage#3437

Open
la14-1 wants to merge 1 commit into
mainfrom
test-fix-telemetry-leak
Open

fix(tests): reset telemetry singleton to prevent cross-test fetch leakage#3437
la14-1 wants to merge 1 commit into
mainfrom
test-fix-telemetry-leak

Conversation

@la14-1
Copy link
Copy Markdown
Collaborator

@la14-1 la14-1 commented May 22, 2026

Why: Fixes 1 consistently failing test in the full suite (hetzner/createServer > cleans up orphaned primary IPs on resource_limit_exceeded and retries). The telemetry singleton's _enabled flag leaked across test files, causing logWarn/logError to fire unexpected fetch() calls that shifted mock counters.

Changes

  • packages/cli/src/shared/telemetry.ts — Added resetTelemetry() export that resets singleton state
  • packages/cli/src/__tests__/telemetry.test.ts — Call resetTelemetry() in afterEach to clean up
  • packages/cli/package.json — Version bump 1.1.0 → 1.1.1

Test plan

  • bun test — 2205 pass, 0 fail (was 2204 pass, 1 fail)
  • bun test telemetry.test.ts hetzner-cov.test.ts — confirms the specific interaction is fixed
  • Biome lint — 0 errors

-- refactor/test-engineer

…est fetch leakage

The telemetry test calls initTelemetry() which sets _enabled=true in the
singleton module. Without resetting, logWarn/logError in subsequent test files
(e.g. hetzner-cov) trigger unexpected fetch() calls via captureWarning/captureError,
shifting mock callCount counters and causing test failures.

Add resetTelemetry() export and call it in telemetry test afterEach.

Agent: test-engineer
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@la14-1 la14-1 marked this pull request as ready for review May 22, 2026 03:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants