-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[Bug]: Async_human_input openai.BadRequestError #1174
Comments
Could you provide steps to reproduce? |
python run example:Agent Chat with Async Human Inputs |
I wasn't able to replicate, but #1182 should shore it up |
Getting the same issue here with a very basic set-up (group chat, no tools). I don't believe this issue should be closed until it's confirmed to be fixed? |
@yenif unfortunately not. Here is my setup and stacktrace: https://gist.github.com/hardchor/260e37de715d7335eb9f61c9b075139c |
Some more info on this. The openai client chokes since the My flow is super simple to repro this:
As soon as the "human" replies - the message generated from that reply gets that extra prop which is then sent to the LLM and the openai client refuses the accept it. |
I am seeing the same behaviour with the example here: |
I've also tried the PR , still getting same error as original comment Command I used: |
I can confirm that i have the same errors. Using GPT-3.5 and also the very basic example from async_ |
@sonichi @yenif @hardchor can you please try it on https://github.com/microsoft/autogen/blob/main/notebook/Async_human_input.ipynb because I could not get it to work after installing the 1182 PR and restarting the notebook |
its not working getting same error as mentioned originally.
|
@yenif I guess there is more bug in the async function. Could you check? |
@sonichi yes I guess that will be it |
I'll be able to look at it tonight |
I can confirm that the latest commit (#e7cdae6) fixes this bug for me. I had exactly the same problem as @yoadsn super simple example before doing the latest pull and now it is gone. |
Async still an issue though |
#1201 solves a problem with async functions, could be related |
#1204 should cover everything |
Describe the bug
openai.BadRequestError: Error code: 400 - {'error': {'message': "Additional properties are not allowed ('tool_responses' was unexpected) - 'messages.3'", 'type': 'invalid_request_error', 'param': None, 'code': None}}
Steps to reproduce
No response
Expected Behavior
No response
Screenshots and logs
No response
Additional Information
v0.2.4
The text was updated successfully, but these errors were encountered: