-
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
[Question]: Does file_ids
parameter still exist?
#13099
Comments
It looks like the @classmethod
def from_new(
...
file_ids: Optional[List[str]] = None,
...
) -> "OpenAIAssistantAgent": And within the method: file_dict = _process_files(client, files)
all_file_ids = list(file_dict.keys()) + file_ids This shows that The discrepancy you're experiencing between the Jupyter Notebook and the Telegram bot could be due to environmental differences or dependency versions, though without more specific details, pinpointing the exact cause is challenging. For further assistance, providing more information about your code, the full error message, and details about your setup could be very helpful. This would allow for a more accurate diagnosis and solution.
|
Hi @dxtym, what's the version of your The official document also renames |
@RussellLuo is correct, the API has changed. Still need to update this class (its somewhere on the TODO list 😓 ) |
Thank you @RussellLuo @logan-markewich ! |
Question Validation
Question
I'm uploading documents to a
QueryEngineTool
object and passing that as atool
parameter toOpenAIAssistantAgent
. As a result, I'm getting theTypeError: Assistant.create() got an unexpected keyword argument 'file_ids'
error. When I looked at the reference of the API, I found out that there was nofile_ids
argument being passed. Yet, the same implementation was working correctly on Jupyter Notebook (this one's a part of Telegram bot, by the way). I checked the versions for LlamaIndex of both ways and they were the same: 0.10.30. Is that internal thing or something's wrong with my code?Thank you for your response.
The text was updated successfully, but these errors were encountered: