Getting Error on this step "python -m local.ingest" #198
-
|
This is the error message I get when i try to run "python -m local.ingest" module requests.exceptions.MissingSchema: Invalid URL '/embeddings': No scheme supplied. Perhaps you meant https:///embeddings? what could be problem, please help me |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 10 replies
-
|
I am getting same, please suggest what can be done DEBUG: 2024-06-02 17:48:21,524 - qdrant:get_collections:166 - [Qdrant] Fetching collections |
Beta Was this translation helpful? Give feedback.
-
|
Hi All,
We will get back on these soon. Thanks for reaching out.
Thanks,
Anuraag
…On Sun, 2 Jun, 2024, 18:05 HariHaran, ***@***.***> wrote:
I am getting same, please suggest what can be done
DEBUG: 2024-06-02 17:48:21,524 - qdrant:get_collections:166 - [Qdrant]
Fetching collections
DEBUG: 2024-06-02 17:48:21,524 - qdrant:get_collections:168 - [Qdrant]
Fetched 0 collections
DEBUG: 2024-06-02 17:48:21,524 - qdrant:create_collection:43 - [Qdrant]
Creating new collection docs
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in
*run_code File "C:\Hari\MyProjects\Python\cognita\local\run.py", line 3,
in from backend.modules.query_controllers import BasicRAGQueryController
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\query_controllers_init*.py",
line 1, in
from backend.modules.query_controllers.example.controller import
BasicRAGQueryController
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\query_controllers\example\controller.py",
line 18, in
from backend.modules.metadata_store.client import METADATA_STORE_CLIENT
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\metadata_store\client.py",
line 4, in
METADATA_STORE_CLIENT =
get_metadata_store_client(config=settings.METADATA_STORE_CONFIG)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\metadata_store\base.py",
line 212, in get_metadata_store_client
return METADATA_STORE_REGISTRYconfig.provider
<http://config=config.config>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\metadata_store\local.py",
line 69, in *init*
VECTOR_STORE_CLIENT.create_collection(
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\vector_db\qdrant.py",
line 46, in create_collection
partial_embeddings = embeddings.embed_documents(["Initial document"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\embedder\embedding_svc.py",
line 44, in embed_documents
return self.call_embedding_service(texts, "documents")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita\backend\modules\embedder\embedding_svc.py",
line 38, in call_embedding_service
response = requests.post(self.url.rstrip("/") + "/embeddings",
json=payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\api.py",
line 115, in post
return request("post", url, data=data, json=json, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\api.py",
line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\sessions.py",
line 575, in request
prep = self.prepare_request(req)
^^^^^^^^^^^^^^^^^^^^^^^^^
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\sessions.py",
line 484, in prepare_request
p.prepare(
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\models.py",
line 367, in prepare
self.prepare_url(url, params)
File
"C:\Hari\MyProjects\Python\cognita.venv\Lib\site-packages\requests\models.py",
line 438, in prepare_url
raise MissingSchema(
requests.exceptions.MissingSchema: Invalid URL '/embeddings': No scheme
supplied. Perhaps you meant https:///embeddings?
—
Reply to this email directly, view it on GitHub
<#198 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADKJQF52VKA7T3SFT7JW2ALZFMGRHAVCNFSM6AAAAABIVAXZWOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMMZXG42TA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Apologies for inconvenience, we were in process of updating the docs and making local setup quick and easy. The README is now updated. You need an Embedding service such as Infinity for ingestion to work. We have added the instructions in the README. You can now use the docker-compose where everything is preset for you, this will automatically run the ingestion and open up the frontend. If you want to use, locally (a bit of hustle, but if you want to :P), you need to setup the infinity-service. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help @S1LV3RJ1NX I've successfully built my project using docker-compose, and all components seem to be running smoothly. However, I've encountered a problem with the frontend: the lists in the add datasource and collection datas are not being populated, despite the backend API and Infinity server API functioning correctly. I've attempted to manually connect the frontend to the backend API, but it doesn't seem to be reflecting the changes. I'm unsure where the issue lies. Could you please provide guidance on how to troubleshoot this problem and ensure proper connectivity between the frontend and backend APIs? |
Beta Was this translation helpful? Give feedback.
-
|
When you run locally, the current UI does not support collection creation and data source addition, everything is routed th' |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification regarding the current limitations of the UI. Could you please provide guidance on how to query against the collection? Specifically, I would like to understand the process and any necessary steps or configurations required to perform queries under the current setup. |
Beta Was this translation helpful? Give feedback.
-
|
once you start the docker-compose, the collection in |
Beta Was this translation helpful? Give feedback.
-
|
I understand but docsQA page not showing indexed collection, instead it's asking to create a new collection. |
Beta Was this translation helpful? Give feedback.
-
|
can you tell me the steps you have followed? @HariHaranDFX |
Beta Was this translation helpful? Give feedback.
-
|
steps I have followed are after you updated for docker
but when I wanted to use it query in frontend it's asking to created new collection as I mentioned before |
Beta Was this translation helpful? Give feedback.
-
|
@S1LV3RJ1NX please can you help me with this? |
Beta Was this translation helpful? Give feedback.
-
|
Not sure, what's the issue here, once you open the FE, it should start working, maybe model download is in progress. We are updating the conditions to account for such cases, FE will start only when all services are up and running and healthy. Keep an eye on #213 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @S1LV3RJ1NX, I hope you are doing well. I have setup Cognita using docker-compose its successfull, I am also running ollama and infinity in docker too all are up and running. models_config.yaml
Error stack: cognita-backend | INFO: 2024-06-25 13:22:01,691 - collection:create_collection:70 - Creating collection dfxwebsite... |
Beta Was this translation helpful? Give feedback.
-
|
Can you take the latest pull and rebuild the image and check. This issue must have been solved. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Hariharan,
Could you also share your email? Will invite you to the cognita evangelists
internal slack.
Thanks!
…On Tue, 25 Jun, 2024, 22:22 Prathamesh Saraf, ***@***.***> wrote:
Can you take the latest pull and rebuild the image and check. This issue
must have been solved.
—
Reply to this email directly, view it on GitHub
<#198 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADKJQFY5X2LJDSUZ2OHDY63ZJF4J5AVCNFSM6AAAAABIVAXZWOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNZSGM2DS>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @agutgutia1991, Thank you for the invitation! I’m excited to join the Cognita Evangelists internal Slack. Here’s my email: "[email protected]" Looking forward to connecting with everyone! |
Beta Was this translation helpful? Give feedback.
-
|
Sent the invite! |
Beta Was this translation helpful? Give feedback.
-
|
Hello @HariHaranDFX Hope you are doing well. Are you still facing this issue? |
Beta Was this translation helpful? Give feedback.
Apologies for inconvenience, we were in process of updating the docs and making local setup quick and easy. The README is now updated. You need an Embedding service such as Infinity for ingestion to work. We have added the instructions in the README.
You can now use the docker-compose where everything is preset for you, this will automatically run the ingestion and open up the frontend.
If you want to use, locally (a bit of hustle, but if you want to :P), you need to setup the infinity-service.
Create a copy of
compose.envfile as.envfile and populate the environment varsEMBEDDING_SVC_URL&RERANKER_SVC_URLwith the url of the service. Then run the ingestion command.