-
Notifications
You must be signed in to change notification settings - Fork 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
[BUG] Watsonx as embedder is not working - script errors and stops #1790
Comments
any solutions? |
I'm having this exact same issue using Ollama, and I'm using crewai version: 0.86.0. |
Sadly this was not fixed by #1804 |
I've applied the similar fix from #1804 to
(addition of I haven't been able to validate if it works beyond that yet, will test and update comments. |
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Some solution here? |
This appears to have been fixed now for crew scoped knowledge_sources. However getting this error when I try at the agent level:
|
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Some solution here? |
@VictorCostaOliveira - this works for me since moving to 0.105.0 |
Tks :), i will test |
@VictorCostaOliveira @mtcolman did you find a fix? or help out with this similar issue! When using CrewAI with knowledge sources, I'm encountering an embedding dimension mismatch error if I've previously used a different embedding model in the same project. This appears to happen because CrewAI uses ChromaDB as its default vector database, and ChromaDB enforces consistent embedding dimensions across operations.
The issue shows up as a dimension mismatch error (e.g., 768 vs 1536) between current embeddings and previously stored embeddings. Steps to Reproduce
Expected BehaviorThe project should either:
Current BehaviorThe project fails with a cryptic ChromaDB error about dimension mismatch that is confusing since there's no clear indication that CrewAI is using ChromaDB under the hood. I've tried running the suggested command Help NeededHas anyone encountered this issue and found a reliable solution? I need a way to either:
Environment
Additional ContextThis issue typically happens when:
Any help would be greatly appreciated as this is blocking my development workflow. |
Description
I'm following https://docs.crewai.com/concepts/knowledge#embedder-configuration and it states:
I try running my crew with this configuration (as I want to use Watsonx for embedder):
Which is inline with the guidance given here: https://docs.crewai.com/concepts/memory#using-watson-embeddings.
However it always errors and asks me for the OpenAI API key:
Steps to Reproduce
See previous detail
Expected behavior
I expect Watsonx embedding to be used, and not be asked for openAI API key.
Screenshots/Code snippets
Given in description
Operating System
Ubuntu 22.04
Python Version
3.10
crewAI Version
0.83.0
crewAI Tools Version
0.14.0
Virtual Environment
Venv
Evidence
Given in description
Possible Solution
Correctly use the watsonx embedding.
https://github.com/crewAIInc/crewAI/blob/v0.83.0/src/crewai/knowledge/storage/knowledge_storage.py#L131
https://github.com/crewAIInc/crewAI/blob/v0.83.0/src/crewai/utilities/embedding_configurator.py#L21
Additional context
Might be linked to #1770
If looks like the code tagged as 0.83.0 (https://github.com/crewAIInc/crewAI/blob/v0.83.0/src/crewai/crew.py#L283) is configured for crew to have the
knowledge
parameter, but not theknowledge_sources
parameterhowever, on the
main
branch (https://github.com/crewAIInc/crewAI/blob/main/src/crewai/crew.py#L201 and https://github.com/crewAIInc/crewAI/blob/main/src/crewai/crew.py#L282) I can see:The text was updated successfully, but these errors were encountered: