Skip to content

chore: record error-tracking autocapture receiver in setup baseline - #70903

Closed
rnegron wants to merge 1 commit into
masterfrom
worktree-fix-error-tracking-receiver-baseline
Closed

chore: record error-tracking autocapture receiver in setup baseline#70903
rnegron wants to merge 1 commit into
masterfrom
worktree-fix-error-tracking-receiver-baseline

Conversation

@rnegron

@rnegron rnegron commented Jul 14, 2026

Copy link
Copy Markdown
Member

Problem

Master has been red on Backend CI since feat(error-tracking): move autocapture opt-in to settings (phase 1) merged. That PR added a new post_save receiver (mirror_autocapture_opt_in_to_settings) that connects at django.setup(), but didn't record it in the committed startup-receiver baseline. test_setup_receivers_match_baseline pins the exact set of first-party receivers wired at setup, so the unrecorded one fails the guard on every master run.

Changes

  • Add the one receiver line to posthog/test/setup_receivers_baseline.txt, in sorted position.

The receiver's wiring is already correct (import-light signals.py imported from ErrorTrackingConfig.ready() with # noqa: F401), and test_no_new_heavy_imports_at_setup still passes, so recording it is the right fix rather than restructuring.

How did you test this code?

  • Reproduced the guard's django.setup() receiver capture in a clean subprocess and confirmed the updated 217-line baseline is a zero-diff exact match for the live receiver set.
  • Did not run the full pytest test locally: my dev shell exports DEBUG=1, which leaks a settings warning onto the subprocess stdout and would false-fail the assertion. CI has no such artifact.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

  • Raúl asked me (Claude, via Claude Code) to triage a red-master Slack alert and fix if possible.
  • Invoked the /django-startup-time skill to confirm the guard's intent and that "record in baseline" (not defer/restructure) was the correct fix here.
  • Verified the culprit commit, confirmed the receiver is import-light and ready()-wired, and validated the baseline diff before committing.

@rnegron rnegron self-assigned this Jul 14, 2026
@rnegron rnegron added the skip-agent-review Save $$$, skip auto agent reviews (Greptile) — use for trivial or chore PRs label Jul 14, 2026
@rnegron
rnegron marked this pull request as ready for review July 14, 2026 21:11
@greptile-apps

greptile-apps Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Reviews (1): Last reviewed commit: "chore: record error-tracking autocapture..." | Re-trigger Greptile

@github-actions

Copy link
Copy Markdown
Contributor

🤖 CI report

⚠️ Playwright — 1 failed

🎭 Playwright report · View test results →

1 failed test:

  • password-protected insight sharing (chromium)

These issues are not necessarily caused by your changes.
Annoyed by this section? Help fix flakies and failures and it will go green!

@trunk-io

trunk-io Bot commented Jul 14, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@rnegron

rnegron commented Jul 15, 2026

Copy link
Copy Markdown
Member Author

Replaced by #70869

@rnegron rnegron closed this Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-agent-review Save $$$, skip auto agent reviews (Greptile) — use for trivial or chore PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant