-
Notifications
You must be signed in to change notification settings - Fork 667
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 an option to the file method to check for md5sum #2491
Comments
I was recently looking for such functionality. But files from Ensembl should be hashed using "sum" instead of md5sum. So some flexibility in this regard would also be highly appreciated (maybe with an additional argument on which kind of hash to make?) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
to save a little time, might consider using something faster like sha1 instead of md5 for this |
We might need to support both anyway since the checksums might be provided in either format |
I'll add support for md5, sha256 and sha1 |
After discussion on the nf-core slack, we (@ewels, @mahesh-panchal) think that it would be useful to add a native option to the
file
method to check the integrity of the files that are staged.Using the example shown in the documentation here, an option that might be named
checksum
should allow providing the hash in a similar manner to the code below:The idea will be that the hash of the file is calculated either if the file is staged or if it is already present in the cage by a previous execution and that if the hash does not match the provided by the user an exception is raised, similarly to what happens when
checkIfExists
option is set to true and the file is not found in the system.The text was updated successfully, but these errors were encountered: