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

[PR #3458] [MERGED] fix chroma db + add similarity offset #4288

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

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/3458
Author: @shatfield4
Created: 3/13/2025
Status: ✅ Merged
Merged: 3/17/2025
Merged by: @timothycarambat

Base: master ← Head: fix-chroma-db

📝 Commits (3)

  • 518e265 fix chroma db + add similarity offset
  • 8030c4c patch chroma scoring
  • dbcd196 Merge branch 'master' into fix-chroma-db

📊 Changes

3 files changed (+984 additions, -916 deletions)

View changed files

📝 server/package.json (+1 -1)
📝 server/utils/vectorDbProviders/chroma/index.js (+32 -21)
📝 server/yarn.lock (+951 -894)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #2536

What is in this change?

  • Fixes issue of Chroma not successfully embedding chunks into vector DB
  • Updated Chroma package
  • Rework similarity search function to add offset of 0.1 in order to perform like other vector DBs

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/3458 **Author:** [@shatfield4](https://github.com/shatfield4) **Created:** 3/13/2025 **Status:** ✅ Merged **Merged:** 3/17/2025 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `fix-chroma-db` --- ### 📝 Commits (3) - [`518e265`](https://github.com/Mintplex-Labs/anything-llm/commit/518e265f586d3b6d7d6e78eb8365360669f3bebd) fix chroma db + add similarity offset - [`8030c4c`](https://github.com/Mintplex-Labs/anything-llm/commit/8030c4c20fc21622e39cf4c043b1c579622c54a2) patch chroma scoring - [`dbcd196`](https://github.com/Mintplex-Labs/anything-llm/commit/dbcd196143ce1f7a5f6db540c2fcf92a5c153832) Merge branch 'master' into fix-chroma-db ### 📊 Changes **3 files changed** (+984 additions, -916 deletions) <details> <summary>View changed files</summary> 📝 `server/package.json` (+1 -1) 📝 `server/utils/vectorDbProviders/chroma/index.js` (+32 -21) 📝 `server/yarn.lock` (+951 -894) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [x] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #2536 ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> - Fixes issue of Chroma not successfully embedding chunks into vector DB - Updated Chroma package - Rework similarity search function to add offset of 0.1 in order to perform like other vector DBs ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:35:31 -05:00
yindo closed this issue 2026-02-22 18:35:31 -05:00
yindo changed title from [PR #3458] fix chroma db + add similarity offset to [PR #3458] [MERGED] fix chroma db + add similarity offset 2026-06-05 15:17:48 -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 pull-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#4288
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?