-
Notifications
You must be signed in to change notification settings - Fork 112
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 issue where subscription server data channel closing gives error #354
Fix issue where subscription server data channel closing gives error #354
Conversation
2b83044
to
32f8a48
Compare
6246e7e
to
141dd9e
Compare
1bd60d7
to
5a3faab
Compare
d86eecd
to
94da0c7
Compare
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.
Seems reasonable to me. It's kinda funny we end up with reflect for this, but it seems fine, and better than adding a bunch of new plumbing to generate a single close
call.
I'll wait a couple days in case @matthieu4294967296moineau has anything to add.
Yeah, I don't love the reflect part, although it does solves the problem. The reason I still went with it was because I found the same thing in subscriptionsMap.Unsubscribe(). If we really don't want to reflect then a type cast could likely also solve the problem 🤗 |
Ah, I guess it's not the first then! A cast would be better, but won't work because we don't know the concrete type, right? |
Ah, right! |
yes this is why I used it in a first place to close the channel when unsubscribing The fix looks good to me, I could test it and it worked fine 👍 |
@benjaminjkraft @matthieu4294967296moineau Great! Thanks for the feedback! Let's merge? 🚀 |
Handles errors discussed here: #347 (comment)
I have: