I am having trouble with tokio::sync::mpsc::UnboundedSender
#5259
Unanswered
TheDarkUndoing
asked this question in
Q&A
Replies: 1 comment
-
In general, putting your channels in locks like that is generally not the best way to approach it. Consider letting the channels be owned by a single task via the actor pattern, see also this example. If you need further help, please post the question on URLO. A lot more people view that forum than answer here. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Source:
Expected Behavior:
Once connected, a client should be able to approve an invite to a lobby and continue receiving messages
Current Behavior:
After approving an invite, the invitee ans the inviter receive one more message in total from the server and then communication halts between the two and the server.
At first I thought it was the RWLocks were not being handled correctly but I don't think that is the issue. My current theory is that when cloning an UnboundedSender it messes with the UnboundedReciever or changes the state of the UnboundedSender in the users Hashmap. Any help on this would be greatly appreciated. I've been banging my head against this for a few weeks now.
Beta Was this translation helpful? Give feedback.
All reactions