Repository navigation
feat: add a per-read send_feature_flag_events option to snapshot reads - #1148
Merged
Merged
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-10-29T15:12:10.692068+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
This was referenced Oct 30, 2026
andehen
marked this pull request as ready for review
November 2, 2026 11:26
marandaneto
approved these changes
Nov 2, 2026
marandaneto
left a comment
Member
There was a problem hiding this comment.
The code looks good; no qualifying findings. Verdict: correct.
eli-r-ph
added a commit
that referenced
this pull request
Nov 4, 2026
* docs(mcp): clarify unsigned session token trust (#1151) (cherry picked from commit b4c2e47) * feat: send a flat body from emails.send (#1155) emails.send now posts template_id and distinct_id at the top level of the request body, for the sync and async clients. The server accepts both shapes, so this changes only the wire format. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: e72a2c10-f145-4f7c-8754-a4fcc06a18be (cherry picked from commit f20066e) * chore: Release v7.81.2 [skip ci] (cherry picked from commit 0aec2d9) * Update generated references (cherry picked from commit 14b4d33) * feat: add a per-read send_feature_flag_events option to snapshot reads (#1148) (cherry picked from commit b10c38a) * fix: send flag id and version on locally evaluated $feature_flag_called (#1149) Locally evaluated flags in get_feature_flag(), feature_enabled() and get_feature_flag_result() sent $feature_flag_called without $feature_flag_id or $feature_flag_version, because both were read only from remote /flags metadata. Read them from the local flag definition that produced the value. evaluate_flags() already sent the id for local flags but dropped the definition's version; send it too. (cherry picked from commit e24100b) * chore: Release v7.82.0 [skip ci] (cherry picked from commit b6f8eaf) * Update generated references (cherry picked from commit 0a5417f) * fix(flags): treat concurrent fallback-cache eviction as a cache miss (#1167) * fix(flags): treat concurrent cache eviction as a cache miss * chore: add changeset for fallback cache eviction fix --------- Co-authored-by: Manoel Aranda Neto <marandaneto@gmail.com> (cherry picked from commit 9ebfb87) * fix(flags): stringify regex properties as compact JSON (#1157) Local regex and not_regex matching called str() on the property. (cherry picked from commit 5b50683) * fix(flags): serialize UUID values in flags request bodies (#1156) The flags request body goes straight to DatetimeSerializer without clean(), so a UUID distinct id, group key, or flag property raised TypeError. The SDK swallowed it and returned missing flags without sending a request. Serialize UUIDs as strings, matching what clean() already does for captured events. (cherry picked from commit a239479) * chore: Release v7.82.1 [skip ci] (cherry picked from commit 8c5e9df) * Update generated references (cherry picked from commit fbbd109) * fix(ai): count Gemini tool use prompt tokens as input tokens (#1164) * fix(ai): count Gemini tool use prompt tokens as input tokens Built-in tools (Google Search, URL context) report the retrieved content in tool_use_prompt_token_count, separately from prompt_token_count, so input tokens were under-reported on grounded responses. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Alex Castillo <alex.castillog33@gmail.com> * chore: add changeset for Gemini tool use prompt tokens Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Alex Castillo <alex.castillog33@gmail.com> * fix(ai): keep unbilled Google Search retrieval out of Gemini input tokens tool_use_prompt_token_count is only added to input tokens when the response carries url_context_metadata (billed as input); Search retrieval is not. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(ai): carry Gemini URL context flag across stream chunks URL context metadata can arrive on a different chunk than the final usage_metadata, so the tool-use prompt tokens were dropped in streaming. Track the flag across chunks in the sync and async clients. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(ci): format Gemini clients and refresh API snapshot --------- Signed-off-by: Alex Castillo <alex.castillog33@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: Manoel Aranda Neto <marandaneto@gmail.com> (cherry picked from commit 57b9db8) * chore: Release v7.82.2 [skip ci] (cherry picked from commit 16e99f0) * Update generated references (cherry picked from commit 1dfca27) --------- Signed-off-by: Alex Castillo <alex.castillog33@gmail.com> Co-authored-by: Dustin Byrne <dustin@posthog.com> Co-authored-by: Harley Alexander <43975092+mayteio@users.noreply.github.com> Co-authored-by: releaser-posthog-python[bot] <262414804+releaser-posthog-python[bot]@users.noreply.github.com> Co-authored-by: Anders <754494+andehen@users.noreply.github.com> Co-authored-by: Sarbajit Sengupta <73594751+Sarbajit-Sengupta@users.noreply.github.com> Co-authored-by: Manoel Aranda Neto <marandaneto@gmail.com> Co-authored-by: Luan Taraschi <130802253+luantaraschi@users.noreply.github.com> Co-authored-by: alexcastgonz <82875882+pcbeingused333@users.noreply.github.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
💡 Motivation and Context
Why: sdk-specs #111 adds the requirement "Snapshot feature flag event control" to
evaluate-flags. A caller can now read a flag from anevaluate_flags()snapshot without sending$feature_flag_called, the same wayget_feature_flag(..., send_feature_flag_events=False)does for one flag. posthog-js implements it in PostHog/posthog-js#5252.Changes:
FeatureFlagEvaluations.is_enabled()andget_flag()take a keyword-onlysend_feature_flag_events: bool = True.False, the read sends no$feature_flag_called, including theflag_missingevent for a key that is not in the snapshot. It also does not check or update the dedupe cache, so a later read that sends events, on the snapshot or throughget_feature_flag(), still reports the flag.only_accessed().get_flag_payload(),keys,only(),only_accessed()andevaluate_flags()do not take the option, as the spec says.Decision order: the spec checks the per-read option, then the SDK's client-level feature flag event default, then
True. posthog-python has no client-level default:get_feature_flag()andfeature_enabled()takesend_feature_flag_events: bool = Trueand nothing else. So step 2 does not apply, and the snapshot option mirrors those getters with aTruedefault. The scenarios tagged@requires:flag_event_defaultdo not apply to this SDK.💚 How did you test it?
TestEvaluateFlagsPerReadEventOptioninposthog/test/test_evaluate_flags.pycovers each spec scenario that applies:test_option_false_silences_one_readtest_suppressed_read_leaves_dedupe_untouchedtest_suppressed_read_leaves_single_flag_getter_exposure_intacttest_suppressed_reads_still_count_for_only_accessedtest_suppressed_missing_key_reports_no_missing_flag@requires:flag_event_default)test_option_true_sends_eventschecks that an explicitTruesends.Run locally:
pytest posthog/test --timeout=30: all pass except three fork tests intest_metrics_autocapture.py, which fail the same way onmainin my local full run and pass when that file runs alone.ruff format --checkandruff checkon the changed files, mypy with the baselinemake public_api_check. The snapshot shows the two new keyword arguments.No manual testing in an app.
📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Written with Claude Code from the merged spec, using posthog-js#5252 as a reference. The option defaults to
Trueinstead ofNone, because Python has no client-level default to fall back to and the single-flag getters usebool = True.🤖 Generated with Claude Code