Make tasks_per_node optional - #2157
Conversation
|
Hi @OhadRubin! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Jasha10
left a comment
There was a problem hiding this comment.
Thanks @OhadRubin! Sorry this took so long to review :P
Accept null for tasks_per_node while retaining 1 as the default. This allows Submitit to omit --ntasks-per-node from Slurm submissions. Add regression coverage, documentation, and a news fragment.
|
Thanks @OhadRubin! I took this over, kept |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 991acfdbb2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This pull request fixes #1898
With the latest version of submitit, tasks_per_node became optional. see here.
(need to change requirements.txt as well)