-
Notifications
You must be signed in to change notification settings - Fork 234
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 carveme #1446
base: master
Are you sure you want to change the base?
Add carveme #1446
Conversation
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
Co-authored-by: Björn Grüning <[email protected]>
Can you please reduce the size of the test data? Then please look at the failing linting tests ...
|
https://anaconda.org/bioconda/carveme/files 1.6.1 is the version that you need. |
We now have this error message:
|
You can find the planemo output here: https://github.com/bgruening/galaxytools/actions/runs/9806570824?pr=1446 |
@bgruening, the first time CarveMe runs, it creates a database with Diamond. It seems the error is due to the lack of permissions to write that database in CarveMe's directory because when testing there, it is only allowed to write in the working directory. Do you have any suggestions to work around this? |
In which folder does careme treis to write? Only the CWD is writeable in a container setting - which we are testing here. |
It seems it is inside the CarveMe folder itself. In 'carveme/data/generated/' |
That is not allowed. Galaxy is a multi user system and we need to ensure every user can only write to the current job working dir |
Do you need help here? |
Maybe. The first time CarveMe runs it needs to write in its directory, out of the user's working directory.
I understand this is incompatible with the Galaxy user system, so I am thinking of a way to work around it. One possibility is to have a parallel version of CarveMe just to be compatible with Galaxy, another is to keep just one version of the tool and deal with this issue in the next update, but I am waiting for some feedback on this from collaborators. If you have any suggestions, please let me know.
…________________________________
From: Björn Grüning ***@***.***>
Sent: Saturday, July 13, 2024 7:57 PM
To: bgruening/galaxytools ***@***.***>
Cc: Miguel Alves Magalhaes Teixeira ***@***.***>; Author ***@***.***>
Subject: Re: [bgruening/galaxytools] Add carveme (PR #1446)
Do you need help here?
—
Reply to this email directly, view it on GitHub<#1446 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AV7E3QHHDCWFYQSODLEYYB3ZMF2BHAVCNFSM6AAAAABKLKTBX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGA2DMNJVGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Imho a tool installation should be read-only and during runtime no one should be allowed to write into it. This is necessary for reproducibility and to have clean installation environments. |
I understand that. I will be back on this as soon as possible.
…________________________________
From: Björn Grüning ***@***.***>
Sent: Sunday, July 14, 2024 1:10 PM
To: bgruening/galaxytools ***@***.***>
Cc: Miguel Alves Magalhaes Teixeira ***@***.***>; Author ***@***.***>
Subject: Re: [bgruening/galaxytools] Add carveme (PR #1446)
Imho a tool installation should be read-only and during runtime no one should be allowed to write into it. This is necessary for reproducibility and to have clean installation environments.
—
Reply to this email directly, view it on GitHub<#1446 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AV7E3QC4HFHT6IEML5UMC7DZMJTCZAVCNFSM6AAAAABKLKTBX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGMZDGOJZGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@lhtxa anything we can help here? |
Hi! We will make some other changes that are taking some more time. Should I keep this branch, or is it better to remove it until we move forward with the changes we need to implement?
…________________________________
From: Björn Grüning ***@***.***>
Sent: Thursday, August 15, 2024 6:09 PM
To: bgruening/galaxytools ***@***.***>
Cc: Miguel Alves Magalhaes Teixeira ***@***.***>; Mention ***@***.***>
Subject: Re: [bgruening/galaxytools] Add carveme (PR #1446)
@lhtxa<https://github.com/lhtxa> anything we can help here?
—
Reply to this email directly, view it on GitHub<#1446 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AV7E3QGOMNNAU3JN3PBVQKDZRTOGJAVCNFSM6AAAAABKLKTBX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRG4ZTQMRVGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @lhtxa, you can mark this PR as draft. Please feel to let us know if you know any help with the tool integration. |
Hi @bgruening !
I saw your previous comments, it just took me a little time to review and fix the issues.
Thank you for the suggestions, here is the updated wrapper.