[FIX] : missing import for parseAuthHeader in server/utils/vectorDbProviders/chroma/index.js
#869
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
😮💨 Thank you @gabrielkoo . Ping in Discord for a contributor badge! Im in there under the same name |
cabwds
pushed a commit
to cabwds/anything-llm
that referenced
this pull request
Jul 3, 2025
…bProviders/chroma/index.js` (Mintplex-Labs#869) fix: import parseAuthHeader in chroma/index.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Type
Relevant Issues
Resolves an error when Chroma is set up with an API key.
What is in this change?
Imports
parseAuthHeaderinserver/utils/vectorDbProviders/chroma/index.jsso that
Chroma.connectwould no longer throw an error.anything-llm/server/utils/vectorDbProviders/chroma/index.js
Lines 17 to 29 in fde905a
Additional Information
Add any other context about the Pull Request here that was not captured above.
Developer Validations
yarn lintfrom the root of the repo & committed changes