The Wire · Showcase
PYTORCH ROLLS BACK NAMED TENSOR REMOVAL, FIXES CHROMIUM PROFILER LEAK
By RepoJournal · Filed · About PyTorch
PyTorch reverted a breaking change that tanked internal signals, while the core team patched a profiler bug that was nuking outer event context.
The named tensor removal [1] is back after it broke internal infrastructure, a significant signal that the community still depends on this API. In parallel, the profiler team fixed a scoped Chromium event bug [2] where exiting a nested profiling context was wiping the entire thread-local event stack, collapsing outer events in the process. On the schema front, error messages for future annotations now surface the actual NameError [3] instead of swallowing it behind a bare exception handler, making debugging type resolution issues dramatically less painful. Inductor's accumulate_grad op got a state modeling fix [4] that makes functionalization explicit: the op now takes current grad as input and returns updated grad, killing hidden Tensor.grad reads that were breaking compiled autograd. The XPU team also standardized their oneDNN integration [5], swapping C API calls for C++ equivalents in DnnlExt.h to eliminate the inconsistent mixing of styles. TensorRT's dependency lockfile got a routine update.
Action items
- → Test internal code paths that use named tensors before next release cycle pytorch/pytorch [plan]
- → Review any custom profiling contexts wrapping chromium_event_timed calls pytorch/pytorch [monitor]
- → Validate accumulate_grad behavior in compiled autograd workflows pytorch/pytorch [plan]
References
- [1] Revert "Remove named tensor (#173895)" pytorch/pytorch
- [2] Fix scoped Chromium event reset (#184973) pytorch/pytorch
- [3] [library] Improve infer_schema error message when future annotations cause NameError (#185694) pytorch/pytorch
- [4] Fix functional accumulate_grad state modeling (#184082) pytorch/pytorch
- [5] [xpu] Refactor OneDNN C API to C++ API (#184486) pytorch/pytorch
FAQ
- What changed in PyTorch on June 1, 2026?
- PyTorch reverted a breaking change that tanked internal signals, while the core team patched a profiler bug that was nuking outer event context.
- What should PyTorch teams do about it?
- Test internal code paths that use named tensors before next release cycle • Review any custom profiling contexts wrapping chromium_event_timed calls • Validate accumulate_grad behavior in compiled autograd workflows
- Which PyTorch repositories shipped on June 1, 2026?
- pytorch/pytorch