meta-pytorch / meta-pytorch/data
[TODO] Make sure that `fork` complains when buffer becomes too large
Open
Nobody has claimed this yet.
todo
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 179
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 2
Description
This issue is generated from the TODO line
https://github.com/pytorch/data/blob/f102d25f9f444de3380c6d49bf7aaf52c213bb1f/examples/vision/imagefolder.py#L80
cc @VitalyFedyunin
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 in examples/vision/imagefolder.py at line 80, where the TODO about fork and an oversized buffer is recorded. Trace the related fork and buffer handling to determine the expected complaint condition, then verify that the behavior is covered by the relevant data-loading tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100