Skip to content

fix(chroma): default to local profile and correct local port to 8000 - #2055

Open
krishking02 wants to merge 1 commit into
rocketride-org:developfrom
krishking02:fix/chroma-default-local
Open

fix(chroma): default to local profile and correct local port to 8000#2055
krishking02 wants to merge 1 commit into
rocketride-org:developfrom
krishking02:fix/chroma-default-local

Conversation

@krishking02

@krishking02 krishking02 commented Aug 19, 2026

Copy link
Copy Markdown

What

The Chroma vector store node defaults to cloud profile with port 8330. 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:

  1. The default profile is cloud, which requires ChromaDB Cloud credentials most users don't have yet
  2. The default local port is 8330, but ChromaDB's actual default is 8000

Both issues are silent — no error message tells you what to change.

Fix

  • Default profile: cloudlocal
  • Default local port: 83308000
  • Updated README schema table to match

Testing

Verified locally: after this change, a fresh RAG Chat pipeline with Chroma connects to a local chroma run instance on first try without any config changes.

Summary by CodeRabbit

  • Bug Fixes
    • Updated the default local Chroma connection port to 8000.
    • Changed the default Chroma profile from cloud to local.

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
@github-actions github-actions Bot added the module:nodes Python pipeline nodes label Aug 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor
🤖 Internal: Discord sync marker

Auto-managed by the Discord notification workflow. Stores the linked Discord message ID and forum thread ID. Do not edit or delete.

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9d39f684-7cce-4b71-8e0f-9cdb08c0c237

📥 Commits

Reviewing files that changed from the base of the PR and between ec24643 and d6e0c5e.

📒 Files selected for processing (1)
  • nodes/src/nodes/store_chroma/services.json

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.


📝 Walkthrough

Walkthrough

The Chroma service configuration changes the default local port from 8330 to 8000 and changes the default profile from cloud to local.

Changes

Chroma service defaults

Layer / File(s) Summary
Local Chroma defaults
nodes/src/nodes/store_chroma/services.json
The default vector.local.port changes to 8000. The default chroma.profile changes to local.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to d6e0c

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: jmaionchi, rod-christensen, stepmikhaylov

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main changes to the Chroma default profile and local port.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.json

File 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module:nodes Python pipeline nodes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant