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

[PR #4705] [MERGED] Modify ChromaCloud provider to check base limitations of chroma cloud before upsert to prevent 422 #4721

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

📋 Pull Request Information

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

Base: master ← Head: 4704-chroma-cloud-quota-apply

📝 Commits (2)

  • f0410c4 Modify ChromaCloud provider to check base limitations of chroma cloud before upsert to prevent 422
  • d0a211d update comments

📊 Changes

3 files changed (+149 additions, -36 deletions)

View changed files

➖ server/utils/vectorDbProviders/chroma/CHROMA_SETUP.md (+0 -28)
📝 server/utils/vectorDbProviders/chroma/index.js (+27 -5)
📝 server/utils/vectorDbProviders/chromacloud/index.js (+122 -3)

📄 Description

Pull Request Type

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

Relevant Issues

resolves #4704

What is in this change?

  • On ChromaCloud vector DB apply base quota limits
  • Duplicate methods on base Chroma provider with no meaningful change to ops since self-hosted don't have these limits
  • Modify the response API to ignore result of add/delete. new API throws on failure, which will be caught at higher level anyway.

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/4705 **Author:** [@timothycarambat](https://github.com/timothycarambat) **Created:** 12/3/2025 **Status:** ✅ Merged **Merged:** 12/3/2025 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `4704-chroma-cloud-quota-apply` --- ### 📝 Commits (2) - [`f0410c4`](https://github.com/Mintplex-Labs/anything-llm/commit/f0410c40863c6645b79ee4e6e5cc92438721074b) Modify ChromaCloud provider to check base limitations of chroma cloud before upsert to prevent 422 - [`d0a211d`](https://github.com/Mintplex-Labs/anything-llm/commit/d0a211d160a0b187147af2efd00fd36e827b9048) update comments ### 📊 Changes **3 files changed** (+149 additions, -36 deletions) <details> <summary>View changed files</summary> ➖ `server/utils/vectorDbProviders/chroma/CHROMA_SETUP.md` (+0 -28) 📝 `server/utils/vectorDbProviders/chroma/index.js` (+27 -5) 📝 `server/utils/vectorDbProviders/chromacloud/index.js` (+122 -3) </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 #4704 ### What is in this change? - On `ChromaCloud` vector DB apply base quota limits - Duplicate methods on base Chroma provider with no meaningful change to ops since self-hosted don't have these limits - Modify the response API to ignore result of add/delete. new API throws on failure, which will be caught at higher level anyway. <!-- Describe the changes in this PR that are impactful to the repo. --> ### 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:36:24 -05:00
yindo closed this issue 2026-02-22 18:36:24 -05:00
yindo changed title from [PR #4705] Modify ChromaCloud provider to check base limitations of chroma cloud before upsert to prevent 422 to [PR #4705] [MERGED] Modify ChromaCloud provider to check base limitations of chroma cloud before upsert to prevent 422 2026-06-05 15:20:02 -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#4721
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?