Skip to content
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

OpenAPIServiceConnector does not support the v2.9.x ChatMessage structure #8774

Open
1 task done
richardpaulhudson opened this issue Jan 27, 2025 · 4 comments · May be fixed by #8817
Open
1 task done

OpenAPIServiceConnector does not support the v2.9.x ChatMessage structure #8774

richardpaulhudson opened this issue Jan 27, 2025 · 4 comments · May be fixed by #8817
Assignees
Labels
P2 Medium priority, add to the next sprint if no P1 available type:bug Something isn't working

Comments

@richardpaulhudson
Copy link
Contributor

Describe the bug
From v2.9.0 tool calls and message texts are separated in the ChatMessage structure. However, OpenAPIServiceConnector has not been updated to support the new structure.

Error message
ValueError: The provided ChatMessage has no text

Expected behavior
OpenAPIServiceConnector should retrieve the tool call information from the tool_calls attribute rather than from the text attribute.

To Reproduce
Try and use OpenAPIServiceConnector in conjunction with the v2.9.0 ChatMessage structure.

FAQ Check

System:

  • OS: MacOS
  • GPU/CPU: CPU
  • Haystack version (commit or version number): 2.9.0
  • DocumentStore: N/A
  • Reader: N/A
  • Retriever: N/A
@anakin87
Copy link
Member

Thanks for reporting this...

In general, I think that in the long run this component could be replaced but in the meantime, we should probably get it working properly again.

Can I ask you for some high-level information about your use case?

@anakin87 anakin87 added the type:bug Something isn't working label Jan 27, 2025
@richardpaulhudson
Copy link
Contributor Author

Hi @anakin87, thanks for your swift reply. It's true that this component is something of a nice to have, but it's a very useful one so it would be a shame to see it disappear.

The point is that OpenAPI is a standard way of describing APIs that extends beyond the context of LLMs and AI. This means that in a large organisation, when we as the team responsible for AI and Machine Learning want to make REST services exposed by other teams available for function calling, we can simply ask the other team to send us the OpenAPI description of their service and load that description into this component. It typically works more or less immediately without significant changes and without us needing to develop a detailed knowledge of the service in question.

@anakin87
Copy link
Member

Thank you for the additional information...

What I meant to say is that in the future we may replace this component with a somewhat different, revised and improved version, but we are not going to remove the feature.

In the meantime, we will try to fix the bug.

@vblagoje
Copy link
Member

I can take this one @julian-risch @anakin87

@julian-risch julian-risch added the P2 Medium priority, add to the next sprint if no P1 available label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Medium priority, add to the next sprint if no P1 available type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants