Skip to content

fix: honor telemetry consent changes in running processes - #17

Merged
fitz2882 merged 2 commits into
mainfrom
codex/security-remediation-core
Sep 5, 2026
Merged

fix: honor telemetry consent changes in running processes#17
fitz2882 merged 2 commits into
mainfrom
codex/security-remediation-core

Conversation

@fitz2882

@fitz2882 fitz2882 commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Running processes could continue collecting and sending funnel telemetry after the effective consent setting changed. Recheck consent on hook, enqueue, flush, and exit paths, discard queued events and accumulated session data when the mode changes, and preserve environment-variable precedence. Document that requests already in flight cannot be recalled.

Validation: 124 focused funnel/core/telemetry tests pass, including empty-queue session metadata after opt-out. Regression cases fail against their previous implementations. A fresh independent reviewer approved the final commit; all 11 CI jobs pass across Python 3.10–3.13, framework integrations, lint, security, and packaging. Tests use mocked senders with no real telemetry or model calls.

@fitz2882
fitz2882 marked this pull request as ready for review September 5, 2026 13:41
@fitz2882
fitz2882 merged commit 0c6c689 into main Sep 5, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant