Skip to content

Conversation

@hexchain
Copy link
Contributor

This relates to...

#4424

Changes

Instead of using origin from the connect and disconnect events, track client using the original key.

Features

N/A

Bug Fixes

#4424

Breaking Changes and Deprecations

N/A

Status

@hexchain hexchain mentioned this pull request Aug 18, 2025
@mcollina
Copy link
Member

Can you add a unit test?

@hexchain
Copy link
Contributor Author

Added a unit test for the referenced issue.

Copy link
Member

@metcoder95 metcoder95 left a comment

Choose a reason for hiding this comment

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

Your report is correct, but I’m not 100% what’s the side effect of it; can you take a look? I’ll try to take a look at it Tomorrow or later this week

@mcollina
Copy link
Member

There are relevant regressions

@hexchain hexchain force-pushed the fix-4424 branch 2 times, most recently from 3f6db98 to e32d948 Compare August 19, 2025 06:45
@hexchain
Copy link
Contributor Author

I've pushed a new version to fix the tests. Some other changes worth noting:

  • In Agent, close is now used instead of destroy after untracking a client
  • connectionError events are also handled now

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm on green CI

Copy link
Member

@gurgunday gurgunday left a comment

Choose a reason for hiding this comment

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

lgtm

@metcoder95 metcoder95 merged commit ab6ea16 into nodejs:main Aug 20, 2025
43 of 44 checks passed
@metcoder95 metcoder95 linked an issue Aug 20, 2025 that may be closed by this pull request
@github-actions github-actions bot mentioned this pull request Aug 22, 2025
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.

Memory leak in Agent

4 participants