meta-pytorch / meta-pytorch/data
Reading services should check if spawn is `fork` and cuda context already initiated.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 179
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 2
Description
🚀 The feature
Instead of runtime we can detect CUDA context fork issues at reading service initiation time and point users to the code mistake.
Motivation, pitch
Lots of users want to do GPU operations inside of DataSet but get confused because of CUDA context behavior at fork.
Alternatives
No response
Additional context
No response
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 locating the reading-service initialization path and the existing handling for fork-based spawning and CUDA context state. Determine how an already-initialized context can be detected there, then add guidance for the offending configuration and tests showing the message appears at initialization rather than runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100