-
Notifications
You must be signed in to change notification settings - Fork 80
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(websocket): lock conflict between emit and poll #213
Conversation
Codecov Report
@@ Coverage Diff @@
## main #213 +/- ##
==========================================
- Coverage 86.77% 86.38% -0.39%
==========================================
Files 30 30
Lines 2351 2358 +7
==========================================
- Hits 2040 2037 -3
- Misses 311 321 +10
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
b80dcf7
to
7a9af9d
Compare
Hi @SSebo, first of all thanks for the contribution and for finding this bug! That is great :) For your PR I am not so sure about the implementation. The async transport never actually locks at the same time, so the only problem is the sync transport. A minimal inversiv and nice change would be to find a way for removing the lock from the sync transport. I assume this should be possible as all methods from the Transport interface only take |
d31b2b5
to
17c8f5e
Compare
@1c3t3a I agree! I found the |
@1c3t3a the code is more reasonable now, 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.
LGTM, thanks a lot!
No description provided.