Superseded by #9 — discovery foundation - #8
Conversation
Introduce the shared generation workload schema that MotionKernel and FastVideo use for baseline measurement, profiling, and end-to-end validation. Ship Wan and LTX manifests, result classification, a resume-friendly launcher bridge, and CPU tests. GPU execution depends on the paired FastVideo generation launcher.
Introduce metadata-only profiling/graph-capture contracts: stable graph fingerprints, operator hotspot ranking, graph-break records, and a pure-tensor allowlist that fails closed on collectives and data-dependent ops. Foundation for universal capture without model-specific annotations.
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Validate launcher resume state JSON, pass mode_env into child processes, reject unknown A/B modes, guard zero optimized medians, reject null wall_seconds, share validators via _validate, and drop machine-local paths from the plan doc.
Superseded by #9, which contains this workstream plus profiler ingestion, full-output validation, FX capture, and impact ranking.