fix: disable ChromaDB telemetry to suppress posthog spam#782
Open
OmkarKirpan wants to merge 1 commit intoMemPalace:developfrom
Open
fix: disable ChromaDB telemetry to suppress posthog spam#782OmkarKirpan wants to merge 1 commit intoMemPalace:developfrom
OmkarKirpan wants to merge 1 commit intoMemPalace:developfrom
Conversation
ChromaDB 0.6.3 with recent posthog versions floods stderr with "Failed to send telemetry event" on every operation. This adds Settings(anonymized_telemetry=False) via a shared CHROMA_SETTINGS constant in backends/chroma.py, used by all PersistentClient construction sites across the codebase. Closes MemPalace#458
OmkarKirpan
requested review from
bensig,
igorls and
milla-jovovich
as code owners
OmkarKirpan
force-pushed
the
fix/disable-chromadb-telemetry
branch
from
377db98 to
bb661b4
Compare
igorls
added
area/cli
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
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.
Summary
Closes #458
Every ChromaDB operation in mempalace 3.1.0+ floods stderr with posthog telemetry errors:
This PR:
CHROMA_SETTINGS = Settings(anonymized_telemetry=False)constant inbackends/chroma.pyPersistentClientconstruction sites across 6 files to use itSharedSystemClientsingleton conflict)Files changed
mempalace/backends/chroma.py— defines the shared constant, uses itmempalace/mcp_server.py— imports and usesCHROMA_SETTINGSmempalace/cli.py— usesCHROMA_SETTINGSincmd_repairandcmd_compressmempalace/dedup.py— usesCHROMA_SETTINGSin both client creation sitesmempalace/repair.py— usesCHROMA_SETTINGSin all 3 client creation sitesmempalace/migrate.py— usesCHROMA_SETTINGSin both client creation sitestests/test_backends.py— verification client usesCHROMA_SETTINGStests/test_mcp_server.py— test helper usesCHROMA_SETTINGSTest plan
pytest tests/test_backends.py tests/test_mcp_server.py::TestCacheInvalidation tests/test_cli.py— 53 passed)ruff checkandruff formatcleanmempalace mine/mempalace statusno longer prints telemetry errors to stderr