oneapi-src / oneapi-src/unified-runtime
Info queries for interop objects fail silently
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
Objects that have been created with interop APIs often lack important pieces of information, required for info queries. For example, urEventCreateWithNativeHandle expects a native CUDA handle, and the resulting event handle will lack a reference to a UR queue. However, urEventGetInfo has no checks for whether an object was created with a native API or not, neither it will return an error in that case. Instead the returned queue handle will be invalid, i.e. == nullptr:
Contributor guide
No contributing guide indexed for this repository
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 in source/adapters/cuda/event.cpp at lines 160-183 and trace how urEventGetInfo handles events created through native interop APIs. Check the related interop object state and determine the expected error behavior for unavailable information; done means native-created events no longer return invalid handles silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100