Runtime and Device-op have same correlation id but with different external id
Open
Nobody has claimed this yet.
bug
plugin
- Dominant language
- C++
- Stars
- 993
- Forks
- 270
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 12
Description
I get this warning in the tensorboard logs when loading a trace:
W0211 00:32:58.057393 140172232447808 event_parser.py:113] Runtime and Device-op have same correlation id 797413 but with different external id
! (runtime external_id, device external_id): (0, 369908)
What does this mean? This is with torch 1.10 and the most recent pip version of the tensorboard plugin.
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 with event_parser.py:113 and the trace-loading path used by the TensorBoard plugin. Reproduce the warning with the reported torch 1.10 setup, then inspect how runtime and device operations correlate their external IDs. Done means establishing whether the warning reflects malformed trace data or a parser bug and documenting the resulting behavior or fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- observability, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100