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
add cellprofiler v4.2.1 tool #1163
Conversation
sunyi000
commented
Sep 15, 2021
- main module of cellprofiler 4.2.1 as galaxy tool
@bgruening I still get all tests passed on my local machine with clean setup, but failed during CI.
just want to see if changing python version in ci.yml makes any difference thanks very much |
Please run your tests locally with |
it succeeded. all 4 tests passed with |
Co-authored-by: Cristóbal Gallardo <gallardoalbac@gmail.com>
Co-authored-by: Cristóbal Gallardo <gallardoalbac@gmail.com>
I just updated the recipe, and created a PR 30645 |
You can ask here for a review https://gitter.im/bioconda/Lobby |
Could you rename the |
It seems to be a similar error @sunyi000 scikit-image/scikit-image#4664. I think that you will need to create a Docker image in order to solve it. |
thanks for the link.. I will create a docker |
In that case, the reason is that in local don't exist such problems with folder permissions, but in Galaxy, due to security reasons, there are restrictions. Regards. |
Co-authored-by: Simon Bray <32272674+simonbray@users.noreply.github.com>
To clarify this, the tool is writing to $HOME, as you can see from the traceback:
The home directory is often not writable on HPC systems, and never when running in docker. This is fixed by using a profile version >= 18.01 in 884f9e6 What this does is provide a home directory for the job that is within the job working directory, and so is mounted R/W in docker. All new tools should use a profile version that shouldn't be older than about a year or two (see here for the recommendations for submitting tools to the IUC: https://galaxy-iuc-standards.readthedocs.io/en/latest/best_practices/tool_xml.html#tool-profile). |
Great to know, thanks! |
thank you very much for the clarification and all the helps @mvdbeek @gallardoalba |
I was looking for it in the toolshed and realized it wasn't there yet. It looks like all checks are fine. Is there any other thing that's holding up the merge? |
Done! |
Thanks a lot. |