Fix torch version constraint incompatible with torchrl>=0.11.1

[Copilot]

torchrl>=0.11.1 requires torch>=2.11 (torchrl 0.X.Y ↔ torch 2.X.Y convention), but all three hardware extras declared torch<2.11 — a direct conflict. In standalone mode this can be masked by an existing venv, but uv's workspace resolver catches it immediately when model-zoo is added as a workspace member.

Change

• torch<2.11 → torch>=2.11,<2.12 in cpu, cuda, and xpu optional dependencies

# Before
cpu = ["torch<2.11", "torchaudio", "torchvision", ...]

# After
cpu = ["torch>=2.11,<2.12", "torchaudio", "torchvision", ...]

Same fix applied to cuda and xpu extras.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• docs.astral.sh
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Why uv sync --extra=cpu --dev requirement conflit when adding "model-zoo" in the workspace, and no problem when comment out "model-zoo"?

创建自 VS Code。