Open frieda-huang opened 2 weeks ago
The problem is due to the code here. I'm using pgvector for memory bank, but it is not able to retrieve that context from the upstream. Temp solution is to add provider_id="remote::pgvector"
manually.
There is another problem in PGVectorIndex(EmbeddingIndex)
here, it resulted in
pgvector/pgvector.py", line 60, in __init__
self.cursor.execute(
psycopg2.errors.SyntaxError: syntax error at or near "-"
LINE 2: ...LE IF NOT EXISTS vector_store_memory_bank_b2acc8c5-5722-415b...
It could be fixed by using self.table_name = f"vector_store_{bank.identifier.replace('-', '_')}"
This is my yaml file:
version: '2'
built_at: '2024-10-14T22:51:08.838065'
image_name: csye7230-searchagent-stack
docker_image: null
conda_env: csye7230-searchagent-stack
apis:
- inference
- safety
- agents
- memory
- telemetry
providers:
inference:
- provider_id: remote::ollama
provider_type: remote::ollama
config:
host: 127.0.0.1
port: 11434
safety:
- provider_id: meta-reference
provider_type: meta-reference
config:
llama_guard_shield: null
enable_prompt_guard: false
agents:
- provider_id: meta-reference
provider_type: meta-reference
config:
persistence_store:
namespace: null
type: sqlite
db_path: /Users/friedahuang/.llama/runtime/kvstore.db
memory:
- provider_id: remote::pgvector
provider_type: remote::pgvector
config:
host: 127.0.0.1
port: 5432
db: remote::pgvector
user: llamastack_user
password: PASSWORD
telemetry:
- provider_id: meta-reference
provider_type: meta-reference
config: {}
Uh oh, thanks for the helpful details. I will take a look at this today and add a test so we don't break these things again.
Thanks for raising the issue! https://github.com/meta-llama/llama-stack/pull/264 - This should fix the first issue.
Hi, I ran the following examples in
agents
, but it looks like there is a problem with accessing the file content when executingOutput
For example, with
podcast_transcript.py
, I got the following output:Inspecting further, it looks like the following code in
common/execute_with_custom_tools.py
is not returning the correct response.I got the following in
response.response.content
: