90 wires and counting

$ follow PyTorch

Keep up with PyTorch in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-06-15
stories 40

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

PYTORCH FIXES CRITICAL FAKETEN OR EDGE CASE AS EXECUTORCH ADDS ARM TOSA SUPPORT

By RepoJournal · Filed · About PyTorch · Composed from the cited sources · methodology

FakeTensor's constructor fallback broke custom ops without device arguments, potentially blocking symbolic tracing workflows across the ecosystem.

The pytorch/pytorch team shipped a fix [1] for FakeTensor's overly aggressive device kwarg injection, which was failing symbolic tracing on custom operators that don't accept device parameters. This is a silent correctness issue that hits anyone building custom ops without device arguments. Meanwhile, functorch batch rules got a substantial refresh [2] removing xfails and improving coverage for copy view operations, and the CPU and MPS logit implementations now correctly handle edge cases where eps > 0.5 [3], fixing a sign-flip bug that would have silently corrupted numerical results. On the X86 front, deprecated quantization fusion patterns have been removed and moved to torchao , streamlining the inductor codebase. The argmin/argmax fix [4] extends CPU support to match the Triton/GPU path, ensuring boolean tensor reductions compile correctly across all backends. ExecutorchArm backend work [5] adds TOSA dialect implementations for data layout operations (CONCAT, RESHAPE, REVERSE, TILE, TRANSPOSE), expanding mobile deployment options. TorchTitan now enables Expert Parallelism for MoE models in vLLM inference [6], pairing TP on dense layers with EP on experts for better scaling, while simultaneously fixing a critical Qwen3 MoE bug [7] where load balancing hooks weren't registered despite being configured.

Action items

References

  1. [1] Fix FakeTensor constructor fallback for custom ops without device (#185107) pytorch/pytorch ↗
  2. [2] [BE][Ez]: Add missing functorch batch rules for copy views (#187256) pytorch/pytorch ↗
  3. [3] [aten] Fix CPU and MPS logit for eps > 0.5 (#181297) pytorch/pytorch ↗
  4. [4] Fix argmin/argmax on boolean tensors for CPU and non-Triton backends (#185970) pytorch/pytorch ↗
  5. [5] Arm backend: Add TOSA dialect data layout ops ↗ pytorch/executorch
  6. [6] [rl] Enable TP2EP for unified MoE model in vLLM wrapper ↗ pytorch/torchtitan
  7. [7] support gpt-oss PP; fix qwen3 MoE expert bias udpate; some other cleanups ↗ pytorch/torchtitan

Quick answers

What shipped in PyTorch on June 15, 2026?
FakeTensor's constructor fallback broke custom ops without device arguments, potentially blocking symbolic tracing workflows across the ecosystem. In total, 35 commits and 5 pull requests landed.
Who contributed to PyTorch on June 15, 2026?
3 developers shipped this update, including oscarandersson8218, wwwjn, and tianyu-l.
What were the notable PyTorch updates?
Fix FakeTensor constructor fallback for custom ops without device (#185107), [BE][Ez]: Add missing functorch batch rules for copy views (#187256), and [aten] Fix CPU and MPS logit for eps > 0.5 (#181297).