-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed Issue #552 #553
Fixed Issue #552 #553
Conversation
…def and its creation process. Updated respective section in README
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
recheck |
1 similar comment
recheck |
I'm not sure I'm doing the CLA right... sorry for the noise, I'll check again tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this should fix the issue. We can just address any remaining problems with follow-up PRs.
Hi @runame thanks for checking it out. |
Hi! what is the status on this? I can update/resolve the README and figure out the isort issue, that seems all is left |
Alright, now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Andres, thank you for taking ownership of this issue and helping to get our singularity workflow in better shape!
I just caught one small typo but other than that LGTM.
Also, it seems like the yapf test is failing. You can fix the formatting in the converter script by running yapf -i -r -vv -p docker/scripts/singularity_converter.py
Hi Andres, there is a merge conflict left on this PR after we reorganized the documentation. Can you move your documentation updates to the GETTING_STARTED.md under the section Using Singularity Instead of Docker please? link to section |
Dear @priyakasimbeg, thanks for taking another look into this. I see that you've moved some of the
Let me know if this looks OK, and thanks again! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for resolving the merge conflicts! I just caught one unintended change in the README.md. I don't think we want to remove the TLDR pytorch installation instructions. Could you add it back please?
This PR implements the fix proposed in the issue:
Dockerfile
intoSingularity.def
in a way that avoids the%files
command.Singularity.def
(tested on the cluster, works)Note that the PR also includes the generated
Singularity.def
file. This refactoring IMO has several advantages for the end user:spython
, one dependency lessLet me know if you have any comments!
Cheers
Andres