viable/strict/1790807359: [dynamo] Track attribute mutations on Tensor container outputs (#198514)
- PyTorch: 1698 events in the last 90 days
- PyTorch: 1677th Release in the last 90 days
- Previous: earlier the same day · viable/strict/1790805133
What happened
I reviewed the implementation and tests, including the exact Tensor-object identity safeguards and final test placement, and believe this is ready for maintainer review. AI-assisted summary: Tensor outputs inside tuple/list results were not registered for attribute-mutation replay, causing setattr on fresh outputs such as torch.split(...) to graph break. Track direct sourceless Tensor children only when their object…
Summary assembled by rule from the sources below