-
Notifications
You must be signed in to change notification settings - Fork 604
Open
Labels
? - Needs TriageNeed team to review and classifyNeed team to review and classifybugSomething isn't workingSomething isn't working
Description
Version
main (latest), hash b4c0b2b
On which installation method(s) does this occur?
uv-managed venv install, created with `uv sync --extra cu13`.
CUDA 13 backend, Linux x86. This issue also occurs on EOS cluster (Linux aarch64).This seems like a platform-agnostic issue.
Notably, this is using warp-lang v1.11.1, which is currently what we have in uv.lock. (This warning may not appear in containers built with older Warp versions.
Describe the issue
Looks like Warp will be deprecating warp.context soon, and we're getting DeprecationWarnings from it. Creating this issue so we can track a fix for this.
Caller is isolated to somewhere in physicsnemo.datapipes.reader.
Minimum reproducible example
$ uv sync --extra cu13
$ uv run --no-sync ipython
Python 3.13.8 (main, Oct 10 2025, 12:48:21) [Clang 20.1.4 ]
Type 'copyright', 'credits' or 'license' for more information
IPython 9.10.0 -- An enhanced Interactive Python. Type '?' for help.
Tip: IPython 9.0+ has hooks to integrate AI/LLM completions.
In [1]: from physicsnemo.datapipes.readers import Reader
Warp DeprecationWarning: The namespace `warp.context` will soon be removed from the public API. It can still be accessed from `warp._src.context` but might be changed or removed without notice.
Warp DeprecationWarning: The symbol `warp.context.Device` will soon be removed from the public API. Use `warp.Device` instead.Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
? - Needs TriageNeed team to review and classifyNeed team to review and classifybugSomething isn't workingSomething isn't working