Skip to content
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

Fix order of removing elements when client disconnects #2603

Merged

Conversation

Johannes-
Copy link

This PR fixes Issue #2589

Copy link
Contributor

@falkoschindler falkoschindler left a comment

Choose a reason for hiding this comment

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

Thanks a lot for this pull request, @Johannes-!
This one is hard to spot (I guess) and it took me a while to understand the problem. At first I thought the old code should work, because we're deleting from self.elements and not from elements. But both references could point to the same instance, so removing from self.elements is also removing from elements.
Long story short, your change looks absolutely correct. 👍🏻

@falkoschindler falkoschindler added the bug Something isn't working label Feb 24, 2024
@falkoschindler falkoschindler added this to the 1.4.16 milestone Feb 24, 2024
@falkoschindler falkoschindler changed the title fix: order of remove elements Fix order of removing elements when client disconnects Feb 24, 2024
@falkoschindler falkoschindler merged commit 939efba into zauberzeug:main Feb 24, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

_handle_delete of Elements is never called when a Client is deleted
2 participants