mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-11 06:30:03 +00:00
fix(cli,producer): opt-in trial polarity + narrowed-fallback-flag docs (review)
Two non-blocking review notes from Rames, both addressed: 1. Trial polarity inverted to OPT-IN: disableDeParallelRouterTrial → enableDeParallelRouterTrial. renderLocal is exported, so any programmatic consumer (future studio-server path, test harness, distributed runner) previously inherited the trial and its process-wide env-var/module-latch state without knowing to disable it — and concurrent invocation races that state. Now only the CLI's own sequential call sites opt in (the single top-level render, and batch at concurrency 1); everyone else gets no trial by default. The doc comment names the sequential-invocation assumption explicitly. 2. deSelfVerifyFallback semantic narrowing documented at both declarations (RenderCaptureObservability + RenderPerfSummary.drawElement): since the pinned-fallback retry was widened, the flag means verify-triggered SPECIFICALLY — OOM/capture_error fallbacks report false with deFallbackReason carrying the reason. Dashboards keyed on de_self_verify_fallback=true as "any fallback fired" must migrate to de_fallback_reason IS NOT NULL (also called out in the PR body for the observability rebuild to pick up). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
6172d79dc2
commit
b02703b7c9
@@ -40,7 +40,15 @@ export interface RenderCaptureObservability {
|
||||
usePageSideCompositing?: boolean;
|
||||
hasHdrContent?: boolean;
|
||||
browserGpuMode?: string;
|
||||
/** drawElement per-render self-verification tripped → whole render re-ran via screenshot. */
|
||||
/**
|
||||
* drawElement per-render SELF-VERIFICATION tripped (blank/PSNR) → whole
|
||||
* render re-ran via screenshot. NARROWED semantics since the pinned-fallback
|
||||
* retry was widened (review): OOM- and generic-capture-error-triggered
|
||||
* fallbacks report FALSE here, with `deFallbackReason` ∈ {oom,
|
||||
* capture_error}. The "any fallback fired" signal is `deFallbackReason`
|
||||
* being set, NOT this flag — dashboards keyed on `de_self_verify_fallback =
|
||||
* true` as any-fallback must migrate to `de_fallback_reason IS NOT NULL`.
|
||||
*/
|
||||
deSelfVerifyFallback?: boolean;
|
||||
/**
|
||||
* Why the capture-stage retry (self-verify OR the pinned-worker-count
|
||||
|
||||
Reference in New Issue
Block a user