NVIDIA-NeMo / NVIDIA-NeMo/Curator
Semantic Dedup Pairwise IO fails to list files for remote cloud path
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 328
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
Describe the bug
fs.ls(..) for remote cloud paths strips the protocol, which results in subsequent code paths failing
Steps/Code to reproduce bug
Please list minimal steps or code snippet for us to be able to reproduce the bug.
A helpful guide on on how to craft a minimal bug report http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
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 nemo_curator/stages/deduplication/semantic/pairwise_io.py around line 82 and inspect how fs.ls handles a remote cloud path. Reproduce the listing with a remote path and trace the subsequent pairwise I/O flow. Done means remote paths retain the protocol and semantic deduplication can continue without the listing failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100