-
Notifications
You must be signed in to change notification settings - Fork 44
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
awaited receiver is not awoken when messaged send into channel #54
Comments
Do you have a code example of this happening? You shouldn't be polling the receiver in a tight loop like this. |
Well, I wasn't until I observed the behavior. Let me try and get a minimal reproduction of this. |
Thanks! Also thanks for the diagram you made. From a glance this seems to be either some kind of desync in |
Thank you :) Having some trouble getting a very minimal reproduction. Basically it works as expected in a very basic case. |
Ok, closing the issue a multi_threaded test case can only run one task at a time? Thank you @notgull for your response and willingness to help. I really like smol and the crates around it :). |
This commit makes async-channel use the new release of event-listener. Highlights include a marked increase in efficiency and no_std support. Supersedes #54 Signed-off-by: John Nunley <dev@notgull.net>
Hey guys,
I am writing an MQTT client that heavily uses channels for internal communication across Network <-> Handler <-> Client.
In some cases I saw that the client places a message into the channel to handler it is visible that there is a message if the length is checked but the Handler is not always awoken for the processing of the client request.
I Included an image here with some explanation.
This is a test function inside a library which runs on tokio multithreaded.
What could be causing the receiver not to awake?
Thanks in advance
The text was updated successfully, but these errors were encountered: