fix: prevent duplicate debug logs when multiple undici instances exist #4630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #4615 - Prevents duplicate debug logs when both Node.js built-in undici and undici as a dependency are present.
Problem
When using
NODE_DEBUG=undici, debug logs were being duplicated 2-3 times because both Node.js's built-in undici and undici installed as a dependency would subscribe to the same diagnostics channels. Each module instance would independently subscribe, causing the same event to be logged multiple times.Solution
Added
hasSubscriberschecks in the diagnostics channel tracking functions before subscribing:trackClientEvents()- checks client-related channelstrackRequestEvents()- checks request-related channelstrackWebSocketEvents()- checks websocket-related channelsThis ensures that even when multiple module instances exist, only the first instance subscribes to the diagnostics channels, preventing duplicate logs.
Test Plan
debug#undici no duplicatesthat reproduces the issue with multiple module loads🤖 Generated with Claude Code