-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Fix presence events on TCP transport #62827
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
This patch does even more, it fixes a memory leak.
Leaking objects:
The leak was discovered immediately after the update to 3005. Thank you @recmanj |
@dwoz PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with this change but it would be nice to have a test which verifies the presence callbacks are getting called.
@sakateka Just a heads up about the request to add an additional test for this change. |
bump @recmanj are you willing to add test coverage here? |
@Ch3LL on its way |
We're wanting to tag for 3006 this friday. I would really love to try to get this in. Any luck on adding test coverage? |
Will push them tomorrow afternoon, sorry |
…o fix-tcp-presence-events
What does this PR do?
Fixes presence events by removing a client's presence correctly.
What issues does this PR fix or reference?
Fixes: #62826
Previous Behavior
Presence events not fired when salt-minion status changes.
New Behavior
Presence events fired correctly when salt-minion status changes.
Merge requirements satisfied?
Commits signed with GPG?
No