Expose rdzv-conf in torch-run launcher in nemo-run
Open
Nobody has claimed this yet.
Stale
support
- Dominant language
- Python
- Stars
- 258
- Forks
- 113
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
We should expose rdzv-conf in the torch-run launcher similar to how we expose rdzv_backend, rdzv_port and rdzv_id.
This feature request is based on the ticket:
https://requests-navigator.atlassian.net/jira/servicedesk/projects/NFS/queues/custom/237/NFS-402
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 at the torch-run launcher and compare how rdzv_backend, rdzv_port, and rdzv_id are exposed. Done means rdzv-conf is exposed consistently; the issue names no file or test, so locate the relevant launcher tests before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- cli, machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100