so it seems that there is a incompatibility within the json structure.
on the oter hand, if i configure the ollama-provider in continue.dev, i cannot use the api-key from open-webui
Originally created by @gipde on GitHub (Jun 20, 2024).
# Bug Report
## Description
**Bug Summary:**
if i use continue.dev i would like to use embeddings via open-webui like tabautocompletion or chat.
**Steps to Reproduce:**
configuration in continue.dev
```
"embeddingsProvider": {
"model": "nomic-embed-text",
"provider": "openai",
"apiBase": "http://<myIP-of-open-webui>/ollama/api",
"apiKey": "sk-"
}
```
due to recordings, continue.dev transmit the following json fragment
```
{
"model": "nomic-embed-text",
"input":["hello ..."]
}
```
but the api requires json in form of
```
{
"model": "nomic-embed-text",
"prompt": "string"
}
```
so it seems that there is a incompatibility within the json structure.
on the oter hand, if i configure the ollama-provider in continue.dev, i cannot use the api-key from open-webui
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gipde on GitHub (Jun 20, 2024).
Bug Report
Description
Bug Summary:
if i use continue.dev i would like to use embeddings via open-webui like tabautocompletion or chat.
Steps to Reproduce:
configuration in continue.dev
due to recordings, continue.dev transmit the following json fragment
but the api requires json in form of
so it seems that there is a incompatibility within the json structure.
on the oter hand, if i configure the ollama-provider in continue.dev, i cannot use the api-key from open-webui