-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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]: #13834
Comments
The error you're encountering is likely related to memory management issues within the underlying C extensions or libraries used by the
Here's a minimal example to help isolate the problem: from llama_index.legacy.vector_stores.timescalevector import TimescaleVectorStore
# Set up the Timescale service URL
TIMESCALE_SERVICE_URL = "postgres:https://tsdbadmin:<password>@<id>.tsdb.cloud.timescale.com:<port>/tsdb?sslmode=require"
# Create a TimescaleVectorStore instance
try:
vector_store = TimescaleVectorStore.from_params(
service_url=TIMESCALE_SERVICE_URL,
table_name="your_table_name_here",
)
print("Vector store created successfully.")
except Exception as e:
print(f"An error occurred: {e}") Ensure that the pip install timescale-vector If the issue persists, you might need to provide more detailed logs or context for further assistance [1][2]. |
@Banjomaestro this seems like an issue with either your env or the timescale vector store package. Maybe you are missing some core libraries (i.e. not python libraries, but system libraries) on the machine you are running on? It works fine on google colab |
Bug Description
The
vector_store = TimescaleVectorStore.from_params(
service_url=TIMESCALE_SERVICE_URL,
table_name=namespace,
)
function from llama-index-time-scale-vector package doesnt work anymore and returns
Python(50484,0x7ff845a3d7c0) malloc: *** error for object 0x16: pointer being freed was not allocated
Python(50484,0x7ff845a3d7c0) malloc: *** set a breakpoint in malloc_error_break to debug
Abort trap: 6
Version
llama-index==0.10.40
Steps to Reproduce
just use the function, I am on mac intel.
Relevant Logs/Tracbacks
The text was updated successfully, but these errors were encountered: