-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Allow for get_human_input to be async #527
Comments
This feature is added in v0.2.0b1. Could you test it? |
Hello, just curious if anyone ever had complete success with this? I was recently trying to go all async with a chainlit/autogen implementation but ran into this issue. I tried running with v0.2.0b1 and I got a bit further downstream but then ran into the below. NOTE: the code I am currently playing with and what generated the trace below is coming from the chanlit-autogen cookbook: https://github.com/Chainlit/cookbook/tree/main/pyautogen
|
Could you try the latest version? v0.2.15. |
Hello @sonichi, I upgraded to v0.2.15 and again using the autogen example from the chainlit cookbook with human_input_mode="ALWAYS", I am running into this the first time the user_proxy asks for feedback. If I simply return and go with auto_reply, the following message gets created:
That message ultimately ends up in autogen/code_utils and fails at line 65 because of the coroutine type:
Here is the complete stack trace:
I am continuing to look into this but if anything comes to mind for you, please let me know. Thanks! |
Hello @sonichi, I finally found some time to look into this further and the issue is solely with the chainlit cookbook code and autogen async is working perfectly. I will open a PR on the chainlit side to resolve the issue. Thanks for the work you do with autogen, it is truly exciting to work with these capabilities! |
@my3sons @constantinidan can we close this issue? |
Hello @julianakiseleva , from my perspective, this issue can be closed. |
Hi!
Ideally the
get_human_input
should also have the ability to be async. Right now, it seems impossible to have a code that is fully async because of this.To do that, there is a need to async the function
check_termination_and_human_reply
and await the three calls toget_human_input
Thanks
The text was updated successfully, but these errors were encountered: