fix(chroma): default to local profile and correct local port to 8000 - #2055
fix(chroma): default to local profile and correct local port to 8000#2055krishking02 wants to merge 1 commit into
Conversation
The Chroma node defaults to 'cloud' profile, which requires ChromaDB Cloud credentials. Most users starting locally hit a connection failure immediately because they don't have Cloud configured. Changes: - Default profile: cloud -> local (matches typical local development workflow) - Default local port: 8330 -> 8000 (matches ChromaDB's actual default port) - Updated README schema table to reflect new default
🤖 Internal: Discord sync markerAuto-managed by the Discord notification workflow. Stores the linked Discord message ID and forum thread ID. Do not edit or delete. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe Chroma service configuration changes the default local port from ChangesChroma service defaults
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized change corrects Chroma's default profile and local port for the common local-development setup, with no actionable merge-blocking risk remaining after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Biome (2.5.6)nodes/src/nodes/store_chroma/services.jsonFile contains syntax errors that prevent linting: Line 2: Expected a property but instead found '//'.; Line 6: End of file expected; Line 6: End of file expected; Line 6: End of file expected; Line 6: End of file expected; Line 11: End of file expected; Line 11: End of file expected; Line 11: End of file expected; Line 11: End of file expected; Line 16: End of file expected; Line 16: End of file expected; Line 16: End of file expected; Line 16: End of file expected; Line 23: End of file expected; Line 23: End of file expected; Line 23: End of file expected; Line 23: End of file expected; Line 29: End of file expected; Line 29: End of file expected; Line 29: End of file expected; Line 29: End of file expected; Line 35: End of file expected; Line 35: End of file expected; Line 35: End of file expected; Line 35: End of file expected; Line 41: End of file expected; Line 41: End of file expected; Line 41: End of file expected; Line 41: End of file expected; Line 46: End of file expected; Li ... [truncated 2005 characters] ... ; Line 218: End of file expected; Line 219: End of file expected; Line 219: End of file expected; Line 219: End of file expected; Line 222: End of file expected; Line 223: End of file expected; Line 223: End of file expected; Line 223: End of file expected; Line 226: End of file expected; Line 227: End of file expected; Line 227: End of file expected; Line 227: End of file expected; Line 231: End of file expected; Line 232: End of file expected; Line 232: End of file expected; Line 232: End of file expected; Line 235: End of file expected; Line 236: End of file expected; Line 236: End of file expected; Line 236: End of file expected; Line 240: End of file expected; Line 246: End of file expected; Line 246: End of file expected; Line 246: End of file expected; Line 258: End of file expected Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
The Chroma vector store node defaults to
cloudprofile with port8330. Both are wrong for the most common case — a developer running Chroma locally for the first time.Problem
I ran into this while building a RAG pipeline during onboarding. After selecting Chroma in the RAG Chat template, the pipeline immediately failed with "could not connect to a Chroma server" because:
cloud, which requires ChromaDB Cloud credentials most users don't have yet8330, but ChromaDB's actual default is8000Both issues are silent — no error message tells you what to change.
Fix
cloud→local8330→8000Testing
Verified locally: after this change, a fresh RAG Chat pipeline with Chroma connects to a local
chroma runinstance on first try without any config changes.Summary by CodeRabbit
8000.