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 #1625] [MERGED] [FIX] ChromaDB namespace normalization #3726

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

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/1625
Author: @shatfield4
Created: 6/6/2024
Status: ✅ Merged
Merged: 6/6/2024
Merged by: @timothycarambat

Base: master ← Head: 1522-feat-chromadb-support-1

📝 Commits (3)

  • 5d1aac4 chromadb namespace normalization
  • 44b40b0 Merge branch 'master' into 1522-feat-chromadb-support-1
  • ad50e88 update normalization function with more clarity

📊 Changes

1 file changed (+63 additions, -15 deletions)

View changed files

📝 server/utils/vectorDbProviders/chroma/index.js (+63 -15)

📄 Description

Pull Request Type

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

Relevant Issues

resolves #1522

What is in this change?

  • Add namespace normalization to adhere to all new Chroma collection name requirements

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/1625 **Author:** [@shatfield4](https://github.com/shatfield4) **Created:** 6/6/2024 **Status:** ✅ Merged **Merged:** 6/6/2024 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `1522-feat-chromadb-support-1` --- ### 📝 Commits (3) - [`5d1aac4`](https://github.com/Mintplex-Labs/anything-llm/commit/5d1aac4955894027ef7826129e916dbe50e57d07) chromadb namespace normalization - [`44b40b0`](https://github.com/Mintplex-Labs/anything-llm/commit/44b40b0209e2ae6ea1921ab0d00a6ace5cc251a8) Merge branch 'master' into 1522-feat-chromadb-support-1 - [`ad50e88`](https://github.com/Mintplex-Labs/anything-llm/commit/ad50e886bc02fbb44e8a3de20b959b079e1bed73) update normalization function with more clarity ### 📊 Changes **1 file changed** (+63 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `server/utils/vectorDbProviders/chroma/index.js` (+63 -15) </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 #1522 ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> - Add namespace normalization to adhere to all new Chroma collection name requirements ### 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:34:22 -05:00
yindo closed this issue 2026-02-22 18:34:22 -05:00
yindo changed title from [PR #1625] [FIX] ChromaDB namespace normalization to [PR #1625] [MERGED] [FIX] ChromaDB namespace normalization 2026-06-05 15:14:55 -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#3726
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?