RepoJournal
PyTorch

@pytorch

PyTorch and the broader machine-learning ecosystem

Pick a date

  1. Sun 17 may
  2. Mon 18 may
  3. Tue 19 may
  4. Wed 20 may
  5. Thu 21 may
  6. Sat 23 may
  7. Sun 24 may
  8. Mon 25 may
  9. Tue 26 may
  10. Wed 27 may
  11. Thu 28 may
  12. Fri 29 may
  13. Sat 30 may
  14. Sun 31 may
  15. Mon 1 jun
  16. Mon 8 jun
  17. Tue 9 jun
  18. Thu 11 jun
  19. Fri 12 jun
  20. Sat 13 jun
  21. Sun 14 jun
  22. Mon 15 jun
  23. Thu 18 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

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

By RepoJournal · Filed · About PyTorch

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

FAQ

What changed in PyTorch on June 15, 2026?
FakeTensor's constructor fallback broke custom ops without device arguments, potentially blocking symbolic tracing workflows across the ecosystem.
What should PyTorch teams do about it?
Rebuild and test custom ops if using symbolic tracing or FakeTensor workflows • Review CPU/MPS logit usage for eps values and rerun validation • Migrate quantization fusion patterns from X86 inductor to torchao
Which PyTorch repositories shipped on June 15, 2026?
pytorch/pytorch, pytorch/executorch, pytorch/torchtitan

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.