Skip to content

fix: exposure tracking hardening — no lost exposures, right-sized dedup, callback isolation - #237

Open
madhuchavva wants to merge 1 commit into
mc/async-eval-apifrom
mc/callback-dedup-hardening
Open

fix: exposure tracking hardening — no lost exposures, right-sized dedup, callback isolation#237
madhuchavva wants to merge 1 commit into
mc/async-eval-apifrom
mc/callback-dedup-hardening

Conversation

@madhuchavva

@madhuchavva madhuchavva commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Exposure tracking hardening: no lost exposures, right-sized dedup, callback isolation

Stacked on #236 (async evaluation API).

Summary

Fixes three exposure-loss/duplication defects in the multi-user client's tracking path and converges its callback-failure semantics with the JS and Python SDKs.

Callback dispatch stays synchronous on the evaluating thread — deliberate, for durability; these changes are loss-prevention only.

Behavior changes (multi-user client only; changelog-flagged)

  • Tracking/usage callback exceptions are logged instead of propagating; failed exposures retry.
  • Exposure dedup is client-wide and 10,000 entries instead of per-evaluator and 30.

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