fix(ci): baseline llm_prompt and early_access startup receivers#72102
Merged
Conversation
Master is red on test_setup_receivers_match_baseline: three receivers connect at django.setup() but are not recorded in the baseline. - llm_prompt.invalidate_llm_prompt_label_cache (post_save + post_delete), from #71509 - early_access_features.signals.create_waitlist_survey_on_concept_stage, from #65180 Both merged after the baseline was last regenerated (#70613, 2026-07-14). Regenerated via UPDATE_SETUP_RECEIVERS_BASELINE=1. Supersedes the stale partial fix in #71940, which recorded only 1 of the 3.
eli-r-ph
marked this pull request as ready for review
July 17, 2026 23:38
There was a problem hiding this comment.
Trivial, purely additive fix to a test baseline file recording three receivers that were already merged into master via other PRs; no production code or risky territory touched.
- 👍 on the PR from hex-security-app[bot].
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 0L, 0F substantive, 3L/1F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T0 auto-approve: T0-deterministic (3L, 1F, single-area, fix) |
| stamphog 2.0.0b3 | .stamphog/policy.yml @ 4a381aa · reviewed head 70c4d61 |
eli-r-ph
enabled auto-merge (squash)
July 17, 2026 23:44
Contributor
🤖 CI report |
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.
Problem
Master is red on
test_setup_receivers_match_baseline. Three signal receivers connect atdjango.setup()but are not recorded inposthog/test/setup_receivers_baseline.txt, so every PR that merges with master fails the Django startup-budget gate through no fault of its own.Changes
Regenerated the baseline to record the three receivers:
products.ai_observability.backend.models.llm_prompt.invalidate_llm_prompt_label_cache(post_save+post_delete), from feat(prompts): Fetch prompts by label #71509products.early_access_features.backend.signals.create_waitlist_survey_on_concept_stage(post_save), from feat: Coming Soon waitlist surveys (gated) #65180Both merged after the baseline was last regenerated (#70613, 2026-07-14), so master drifted. This supersedes the stale partial fix in #71940, which recorded only 1 of the 3 (it was generated before #65180 landed).
How did you test this code?
Ran
UPDATE_SETUP_RECEIVERS_BASELINE=1 pytest posthog/test/test_startup_import_budget.py -k receivers_matchon a cleanmastercheckout. The diff is exactly the three lines above (no removals, no other additions), and-k receivers_matchthen passes.🤖 Agent context
Autonomy: Human-driven (agent-assisted)
I (Eli, via Cursor agent) hit this while getting an unrelated GRL PR stack green. That stack's Django PR failed CI on these three orphan receivers, which turned out to be pre-existing master breakage, not mine. I cut this isolated fix off
masterso the baseline drift is fixed on its own rather than absorbed into the feature PR. The regen was authoritative (ran the documentedUPDATE_SETUP_RECEIVERS_BASELINE=1command), not hand-edited.