-
Notifications
You must be signed in to change notification settings - Fork 3
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
RuntimeWarning: coroutine 'Queue.put' was never awaited #154
Comments
Thank you for reporting. Indeed, let's leave it open for now in case it occurs again. |
Its seems like the same bug also caused this test run to timeout. |
@danielhollas Do you know for which version this bug was triggered? |
@csadorf version |
As it occurred again? I am having large trouble re-producing the problem. It seems to be somehow related to a premature termination of the process, but I have not been able to pin things down yet. |
I haven't seen it since, but I also haven't been using aiidalab-launch much lately. |
Just noting that I am still randomly seeing this issue. Will probably be a pain to debug... |
I checked the code and it looks like the coroutine 'Queue.put' is only used in a single place - the aiidalab-launch/aiidalab_launch/util.py Line 130 in b8d4da5
Which is in turn used by the aiidalab-launch/aiidalab_launch/__main__.py Line 421 in b8d4da5
Two lines below that the Task is cancelled but it seems that the cancellation will not happen if there is an exception when the container fails to start withing given timeout. I am trying to fix that in #164, but it might be hard to verify that this was indeed the problem (especially since the problem described in this issue appeared even when the container started succcessfully. |
Here's the output of the startup command:
The warning
/usr/lib/python3.8/asyncio/base_events.py:641: RuntimeWarning: coroutine 'Queue.put' was never awaited
was emitted when I pressedn+enter
on the prompt to open the browser. I then needed to send the Ctrl+C signal to get out of the process.This is the first time that this happened to me so likely not very common issue that might be hard to debug. Assigning Low priority for now, will escalate if I keep hitting this.
The text was updated successfully, but these errors were encountered: