dmitrivMS's Description of Work #336369 Followup on memory use by telemetry extraction job
Depends on #336746. Kept as a draft until that declaration-alignment prerequisite lands.
Fixes #336369
Refs microsoft/vscode-telemetry-extractor#80.
Summary
- Update
@vscode/telemetry-extractorfrom 1.20.4 to the published 1.20.5 in the root manifest and lockfile. - Pick up the upstream sequential-worker memory optimization.
- Keep the existing
--max-old-space-size=4096setting and all unrelated dependency resolutions unchanged.
Version 1.20.5 was published on 2026-09-18. Its npm tarball SHA-512 matches the updated lockfile, and the compiled worker is included.
Prerequisite
A dependency-only pickup on main currently fails because the workbench and Agent Host declare conflicting metadata for the same chat.toolApproval event. The new release detects that conflict. #336746 shares the existing classification between both emitters without changing their runtime JavaScript.
This PR deliberately contains only the two dependency files; it must not merge before #336746. No telemetry verification is disabled.
Validation
Using the actual published tarball, Node 24.18.0 / Windows x64, and the existing 4096 MiB setting:
-
With #336746 applied: core extraction succeeds with 485 events and 34 common properties. - The seven-entry extension/helper config succeeds with 72 events and 14 common properties.
- Exact manifest/lockfile checks confirm there are no unrelated dependency changes; published tarball integrity matches.
- Focused extraction-wrapper compilation, wrapper hygiene and
git diff --checkpass. The root JSON manifests are excluded from repository hygiene and were validated structurally.
Existing dependencies were reused read-only; this is not a full CI-agent/filesystem replay. Real macOS memory constraints and CI validation remain part of #336369. No pipeline was queued or rerun.