trace_linker: An error occurred when following the user-guide
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 196
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
A clear and concise description of what the bug is.
Platform:windows11
torch version:2.2.2+cu121
protobuf version:6.31.0(chakra 0.0.4 requires protobuf==5.*)
it's my bug
I found that all my kineto tracking was cpu_op
Steps to Reproduce
Steps to reproduce the behavior.
Please include the version information where the bug was observed.
Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Contributor 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.
Research direction
Start by reproducing the trace_linker user-guide flow on Windows 11 with PyTorch 2.2.2+cu121 and the reported protobuf versions. Inspect the trace_linker entry point and the kineto tracking output shown in the screenshots; completion should explain the failure and establish whether the resulting trace correctly includes more than cpu_op events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100