-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updates to migrate to nf-schema #96
base: dev
Are you sure you want to change the base?
Conversation
Update usage.md
… into dp24_schema_update
|
Are there any plans to get blobtoolkit's schema updated to nf-schema now that nf-validation is depreciated? On Slack it turned out that the reason a user couldn't use ASCC was because nf-validation is depreciated, updating the pipeline to nf-schema fixed it, but then it crashed on BTK because of the same reason. Thankfully, the parts of ASCC that ran were enough to give them the results they needed. However, it raises the issue that nf-validation is depreciated and end-user issues may become more common. Those able to run it may have the nf-validation plugin already cached in the plugin's directory. The only issue with the upgrade seems to be shown in the above run logs, it doesn't like Another issue being that it isn't 100% compatible with NF-Tools and may break linting. |
@DLBPointon . I've now created an issue to have a record: sanger-tol/blobtoolkit#138 Would you say it's something I could squeeze in like an hour ? We're going to release v0.7 soon and then pause development for a bit (we've been expressly asked to work on finalising and deploying the integration of the Genome After-Party), so now is really the time to get it done. |
The nf-schema, yes I think you could get it done in an hour. Most of what you would need to do is in this PR. Happy to sort it for you if you don't have the time. |
#95 Updating from NF-Validation to NF-Schema
This was causing crashes with external users.
Acceptance of PR needs the same done to Blobtoolkit.