Bump warp-lang to 1.13.0 dev nightly#2528
Conversation
Reinstate the nightly bump reverted in newton-physics#2448, pointing at the latest nightly build 1.13.0.dev20260422.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughASV and project dependency pins change to a Warp pre-release ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
warp-lang 1.13.0 dev removed wp.types.scalar_types. Use the new wp.types.is_scalar() helper, which has equivalent behaviour.
Nightly dev20260422 introduces a deterministic SIGSEGV / double-free in the CPU path under graph capture, reproducing across Linux, macOS, Windows, and the CI GPU runner's CPU leg. The crash occurs during garbage collection while mujoco_warp is inside a warp.capture_while region, with stack frames landing in warp._src.context / _src.types. Only dev20260422 is affected; dev20260421 runs the full suite cleanly. Suspected upstream regression: omniverse/warp d11116fc "Add graph capture for APIC serialization and CPU replay [newton-physicsGH-1349]", which is the only newly-included commit in dev20260422 that touches capture machinery on the CPU path. Pin exactly to dev20260421 until a fixed nightly lands; also tighten from >=1.12.0 to the exact nightly to prevent accidental upgrades to the broken build.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pyproject.toml`:
- Around line 30-32: Replace the exact equality pin for warp-lang in
project.dependencies with a minimum-compatible or ranged constraint (e.g. change
"warp-lang==1.13.0.dev20260421" to a minimum like
"warp-lang>=1.13.0.dev20260421" or a ranged form excluding a broken build such
as "warp-lang>=1.13.0.dev20260421,!=1.13.0.dev20260422") to avoid forcing
downstream installs to a single nightly, and add a user-facing CHANGELOG.md
entry under the [Unreleased] → Changed section in imperative present tense (for
example: “Bump `warp-lang` requirement to `1.13.0.dev20260421`” plus any
migration notes) so the runtime bump is documented.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 1754669e-d06c-428d-81ff-16bcc57ee376
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
asv.conf.jsonpyproject.toml
🚧 Files skipped from review as they are similar to previous changes (1)
- asv.conf.json
Dev20260422 regressed the CPU path under graph capture (see prior commit). Advance the pin to the latest nightly to pick up fixes and stay current with upstream warp.
Description
Reinstate the warp-lang nightly bump that was reverted in #2448, pointing at the latest nightly build
1.13.0.dev20260422.Checklist
CHANGELOG.mdhas been updated (if user-facing change)Test plan
Rely on CI to validate the updated nightly against the existing test suite.
Summary by CodeRabbit
Chores
Documentation