RepoJournal
PyTorch

@pytorch

PyTorch and the broader machine-learning ecosystem

Pick a date

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

The Wire · Showcase

DYNAMO BACKENDS UNBROKEN, PYTORCH COMPLETES OSDC MIGRATION

By RepoJournal · Filed · About PyTorch

The ts and aot_ts backends were silently failing since lazy graph modules became default, but dynamo tests masked it until today's fix ships.

Dynamo's critical backends are now working correctly after a fix that forces LazyGraphModule into plain GraphModule before torch.jit.script [1]. The tests masking this default config are also dropped, so the fix covers production use. In parallel, PyTorch completed its infrastructure migration off EC2 to OSDC across three workflows. The docs build [2], stable-fa3 tests [3], and linux build/test workflows [4] all dropped legacy EC2 paths, making OSDC/ARC the sole job. This cleanup removes roughly 150 lines of conditional logic that no longer has a purpose. On the stability front, CUDAGuardImpl now restores current device via RAII on exception paths, fixing a realistic crash case where cudaErrorNotReady would leak device state [5]. TorchTitan's integration CI is now green after fixes to numa API bindings, H100 cache setup, and per-microbatch D2H syncs from isfinite checks [6] [7].

Action items

References

  1. [1] [Dynamo] Fix ts and aot_ts backends with LazyGraphModule (#188875) pytorch/pytorch
  2. [2] Delete EC2 docs build path from _docs, rename build-docs-osdc to build-docs (#189169) pytorch/pytorch
  3. [3] Delete EC2 test path from _linux-test-stable-fa3, rename test-osdc to test (#189170) pytorch/pytorch
  4. [4] Remove the use-arc parameter from linux build/test/docs workflows (#189171) pytorch/pytorch
  5. [5] [c10][cuda] Restore current device via RAII on the throwing path in CUDAGuardImpl (#188167) pytorch/pytorch
  6. [6] [graph_trainer] Fix red CI: numa + H100 HF-cache + OpaqueBase startup breaks, chunked-loss remat scoping, quarantines ↗ pytorch/torchtitan
  7. [7] Avoid per-microbatch D2H caused by isfinite ↗ pytorch/torchtitan

FAQ

What changed in PyTorch on July 8, 2026?
The ts and aot_ts backends were silently failing since lazy graph modules became default, but dynamo tests masked it until today's fix ships.
What should PyTorch teams do about it?
Pull dynamo backend fix [ref:1] to unblock ts/aot_ts users in your next deploy • Review OSDC migration for any custom workflows still targeting EC2 paths [ref:2] [ref:3] [ref:4] • Monitor TorchTitan integration suites for further regressions after CI fixes [ref:6]
Which PyTorch repositories shipped on July 8, 2026?
pytorch/pytorch, 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.