Skip to content

net: always publish to 'net.client.socket' diagnostics channel #58349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

RaisinTen
Copy link
Member

Previously, the 'net.client.socket' diagnostics channel was only published to when net.connect() was called. This change ensures the message is also published for the following calls:

  • net.createConnection()
  • net.Socket#connect()
  • tls.connect()

Previously, the 'net.client.socket' diagnostics channel was only
published to when `net.connect()` was called. This change ensures the
message is also published for the following calls:

- net.createConnection()
- net.Socket#connect()
- tls.connect()

Signed-off-by: Darshan Sen <[email protected]>
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/net

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. net Issues and PRs related to the net subsystem. labels May 16, 2025
@RaisinTen RaisinTen requested a review from theanarkh May 16, 2025 09:00
@nodejs-github-bot

This comment was marked as outdated.

Copy link

codecov bot commented May 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.23%. Comparing base (b197355) to head (9a358bd).
Report is 45 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #58349   +/-   ##
=======================================
  Coverage   90.23%   90.23%           
=======================================
  Files         633      633           
  Lines      186818   186839   +21     
  Branches    36668    36682   +14     
=======================================
+ Hits       168578   168598   +20     
- Misses      11036    11038    +2     
+ Partials     7204     7203    -1     
Files with missing lines Coverage Δ
lib/net.js 95.28% <100.00%> (+<0.01%) ⬆️

... and 35 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@nodejs-github-bot
Copy link
Collaborator

@RaisinTen RaisinTen added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels May 16, 2025
Copy link
Contributor

@ShogunPanda ShogunPanda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label May 18, 2025
@nodejs-github-bot nodejs-github-bot merged commit 9eb9c26 into nodejs:main May 18, 2025
70 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 9eb9c26

@RaisinTen RaisinTen deleted the net-always-publish-to-net.client.socket-diagnostics-channel branch May 18, 2025 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. needs-ci PRs that need a full CI run. net Issues and PRs related to the net subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants