mirror of
https://github.com/langchain-ai/langchain-postgres.git
synced 2026-07-16 01:33:18 -04:00
Lacking CONTRIBUTING.MD #32
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sachin-Bhat on GitHub (Jul 19, 2024).
Hello everyone,
I believe that the project currently lacks instructions on contributing to the project. Would greatly appreciate if there are instructions on setting up poetry and the test environment. This can also help new contributors write and see if their tests work.
Cheers,
Sachin
@amotl commented on GitHub (Jan 29, 2025):
Hi @Sachin-Bhat,
while working on GH-157, the outcome and response to your request is attached below.
With kind regards,
Andreas.
Development Sandbox
Acquire sources and create virtualenv.
Install package, editable.
Start PostgreSQL/PGVector.
Invoke test cases.
@amotl commented on GitHub (Jan 29, 2025):
Hi again. GH-158 includes a relevant patch that adds this information to the repository.
@eyurtsev commented on GitHub (Feb 4, 2025):
Merged
@alberto-agudo commented on GitHub (Jul 8, 2025):
Hi everyone,
I have recently tried to follow the indications of the
DEVELOPMENT.mdfile in a directory from scratch and it seems they return some errors:This is the first crash
which I've solved through
On the other hand, it seems like the Docker container snippet doesn't work properly with pytest. After running the container, pytest tests fail because they can't connect to the DB instance. I think this is related with the port exposed under this config (6024) for the host, because using
docker-compose up pgvector, as specified here https://github.com/langchain-ai/langchain-postgres/blob/18b1bcdb75ed152da717e3d624e1ed822d17d60f/tests/utils.py#L9-L21 does work, and this config exposes port 5432 on the host.Thanks.
Best,
Alberto.
@amotl commented on GitHub (Jul 8, 2025):
Hi Alberto. Thanks a stack for your report. Would you be able to turn that into a patch so we can update the documentation fluently when applicable?