bug: permission issues when overwriting domains_color_file #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As explained in this issue, there are problems with Singularity because the code tries to overwrite the source file.
This is fine if the user has write permissions on that file (as I understand, in the Docker image and Singularity, if you use the --writable argument). However, I think there are better solutions than this (especially when integrating the program into a pipeline).
It is unclear how the code works: is it necessary to overwrite this file? Could you use temporary files? Although I do not have much knowledge, I would say that the program's current behavior (being able to edit a tsv file persistently) could be achieved by creating a "configuration" file in the user's home folder rather than overwriting the source code of the program. I have attached a PR with an initial proposal.