fix: disable ph telemetry still calls posthog#4203
Merged
whysosaket merged 3 commits intomem0ai:mainfrom Mar 3, 2026
Merged
Conversation
This was referenced Mar 21, 2026
This was referenced Mar 24, 2026
jamebobob
pushed a commit
to jamebobob/mem0-vigil-recall
that referenced
this pull request
Mar 29, 2026
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.
This PR fixes an issue where the Posthog client was being instantiated even when telemetry was explicitly disabled via MEM0_TELEMETRY=False.
Although events were not being captured in this state, the client was still initialized unnecessarily, which could:
Create unwanted background threads
Initialize network-related resources
Increase startup overhead
Cause confusion when verifying telemetry is truly disabled