Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4431] [FEAT]: Validate PG Vector Database Connection #2827

New Issue
Closed
opened 2026-02-22 18:31:26 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:31:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @angelplusultra on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4431

Originally assigned to: @angelplusultra on GitHub.

What would you like to see?

Currently, ALLM does not validate the connection details provided for any vector database.
If the connection string is incorrect or the database is unavailable, initiating a chat with an LLM results in a prolonged loading state (in my case, 2 minutes and 35 seconds with a PGVector instance) before the LLM finally responds.

Once the timeout lifts and the LLM proceeds to respond, there’s no indication that the application failed to connect to the user’s vector database. This can easily lead to confusion, as the user might assume the delay is due to the AI provider rather than a database connection issue.

⸻

Proposed Solutions

  1. Validate Connection on Setup

When users provide their vector database connection details in Settings > Vector Database and click Save, the system should attempt to connect immediately:
• If successful: Save the details as usual.
• If unsuccessful: Alert the user that the connection could not be established.

This would catch misconfigurations early. However, it won’t address cases where the database becomes unreachable later, such as during runtime.

⸻

  1. Validate Connection Before Enabling Chat

When a user navigates to a chat session, attempt to connect to their vector database before enabling chat functionality:
• Display a loading state while checking the connection.
• If the connection is successful: Proceed and allow the user to chat.
• If unsuccessful: Alert the user that the database is unreachable instead of leaving them stuck in a long, unexplained loading state.

⸻

  1. Both of the above

This approach would fully resolve the current issue and improve the overall user experience.

Originally created by @angelplusultra on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4431 Originally assigned to: @angelplusultra on GitHub. ### What would you like to see? Currently, ALLM does not validate the connection details provided for any vector database. If the connection string is incorrect or the database is unavailable, initiating a chat with an LLM results in a prolonged loading state (in my case, 2 minutes and 35 seconds with a PGVector instance) before the LLM finally responds. Once the timeout lifts and the LLM proceeds to respond, **there’s no indication that the application failed to connect to the user’s vector database.** This can easily lead to confusion, as the user might assume the delay is due to the AI provider rather than a database connection issue. ⸻ ### Proposed Solutions 1. Validate Connection on Setup When users provide their vector database connection details in Settings > Vector Database and click Save, the system should attempt to connect immediately: • If successful: Save the details as usual. • If unsuccessful: Alert the user that the connection could not be established. This would catch misconfigurations early. However, it won’t address cases where the database becomes unreachable later, such as during runtime. ⸻ 2. Validate Connection Before Enabling Chat When a user navigates to a chat session, attempt to connect to their vector database before enabling chat functionality: • Display a loading state while checking the connection. • If the connection is successful: Proceed and allow the user to chat. • If unsuccessful: Alert the user that the database is unreachable instead of leaving them stuck in a long, unexplained loading state. ⸻ 3. Both of the above This approach would fully resolve the current issue and improve the overall user experience.
yindo added the enhancementfeature request labels 2026-02-22 18:31:26 -05:00
yindo closed this issue 2026-02-22 18:31:26 -05:00
yindo changed title from [FEAT]: Validate PG Vector Database Connection to [GH-ISSUE #4431] [FEAT]: Validate PG Vector Database Connection 2026-06-05 14:48:46 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2827
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?