Problemsby GlyphTrouble with PyTorch device
1 post from 1 person1d activeNew, +1 this weekunverified
Posts per day
The posts behind it
Allow PrivateUse1 devices to opt out of device use in FakeTensorMode
### 🐛 Describe the bug Currently, the logic in `fake_tensor.py:avoid_device_init` simply returns False when PrivateUseBackend1 is available. However, this should be configurable by the backend. We have seen this with the Spyre backend, reported here:...
Companies and products named
About this problem
Evidence
1 post from 1 person in 1 place. Mostly on pytorch/pytorch. Tools named alongside: GitHub.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about PyTorch with no known issue, sharing the word "device". First post Nov 3, 2026, latest Nov 3, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
Other PyTorch problems
PyTorch GPU access and drivers are painful
14 posts from 14 people on GitHub issues.
PyTorch upgrades break working setups
26 posts from 21 people on GitHub issues, Reddit.
PyTorch users keep filing bugs
Top post: "Meta-issue: torch.compile gaps found via the CPython test suite", one of 46 posts from 37 people on GitHub issues, Reddit.
Trouble with PyTorch values
Top post: "How can I sum elements of a tensor based on a condition of one out of two values in its index pair into a new", one of 3 posts from 3 people on GitHub issues, Stack Overflow.
Trouble with PyTorch causing
Top post: "PyVista plotting running slowly, resetting box size and causing collisions", one of 3 posts from 3 people on GitHub issues, Stack Overflow.
PyTorch deprecations force unplanned migrations
8 posts from 5 people on GitHub issues.
Trouble with PyTorch true
Top post: "PaddleOCR-VL: position embedding interpolation changed from align_corners=False to True", one of 9 posts from 6 people on GitHub issues.
Trouble with PyTorch inductor
Top post: "`[Inductor][CPU] torch.var returns NaN for large-magnitude constant float64 inputs while eager returns 0`", one of 12 posts from 9 people on GitHub issues.
PyTorch builds are slow or flaky
9 posts from 1 person on GitHub issues. Unverified.
Trouble with PyTorch input
Top post: "Generation crashes with encoder_repetition_penalty when encoder_outputs are provided without input_ids", one of 6 posts from 6 people on GitHub issues.
Running PyTorch locally hits memory and speed limits
5 posts from 5 people on GitHub issues, Hacker News.
PyTorch lock-in makes switching costly
4 posts from 4 people on GitHub issues.
History