tlparse should report symint specialization in tensor subclass torch_dispatch
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- machine-learning, tooling
Research direction
Reproduce the behavior with the linked TwoTensor gist and inspect the tlparse output for the symint specialization inside torch_dispatch. Trace how the call stack is assembled, then verify that the resulting report identifies the tensor subclass or its specialization location without misattributing the work to the user callsite.
Written by the indexing model from the issue text.
Description
Today, if a specialization for a symint happens inside a tensor subclass's torch_dispatch, we never actually report it in a call stack.
Instead, we see the user callstack, which can be confusing. Repro: run tlparse on the following, https://gist.github.com/zou3519/476a049ffd8070973dd31a4eba9f2ca7 , this produces the following tlparse output:
Now, everytime I see this, I think the stack trace is wrong. Why is torch.cos causing a specialization??. Then, I realize that Tensor subclasses are a thing. I wish here it would tell me what the Tensor subclass is (TwoTensor in this case!) or the LOC at the Tensor subclass that does the specialization.
Not sure if this is possible, but this would really help with debugging vLLM (where Tensor subclasses are now abundant).
cc @chauhang @penguinwu @ezyang @bobrenjc93
- Dominant language
- Rust
- Stars
- 95
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from meta-pytorch/tlparse
-
one-liner to run tlparsePossibly taken @ezyang claimed this 284 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
meta-pytorch/tlparse#162 ·
-
Some way for tlparse to automatically upload into gist for easy sharingMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
meta-pytorch/tlparse#161 · 5 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
meta-pytorch/tlparse#153 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
meta-pytorch/tlparse#142 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
meta-pytorch/tlparse#141 · 1 comment ·
All issues in meta-pytorch/tlparse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Y-ASLant/ElegantClipboard#178 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linxiv-dev/linXiv#384 · 1 comment ·
Maintainers usually reply within 1 day
-
bug drawings ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
userFRM/egui-charts#1595 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
smoltcp-rs/smoltcp#1235 ·
Maintainers usually reply within 1 day
-
scope:core type:security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day