-
Notifications
You must be signed in to change notification settings - Fork 38
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
Make it possible to skip MultiQC #140
Merged
Merged
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7bf7d14
Make it possible to skip multiqc with `--skip_tools`
Aratz 4df539f
Check multiqc report exists in other tests
Aratz 9c92771
Fix old test
Aratz 6664f01
Add test to check MultiQC can be skipped
Aratz e4a1403
Update snapshot
Aratz 1a62427
Add description in schema for `skip_tools`
Aratz c74d5b7
Fix error raising
Aratz 5ba20d8
Add contribution to changelog
Aratz 14f0de7
Fix tests
Aratz c09b873
Merge branch 'dev' into dev
edmundmiller File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interested why you removed the Nextflow.errors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question, when I run it (e.g. by removing a column in the input samplesheet), I get
No such variable: Nextflow
, when I removeNextflow
I get the correct error message. Maybe you could try it on your side to confirm this is not because of some glitch in my setup?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What Nextflow version are you on? Here's the commit that changed it: d271419
@adamrtalbot Could you explain it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on
23.04.3
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly, no! If it doesn't import
Nextflow
anderror
works then go for it! Could be a good chance to add an explicit test for correctly raising an error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other way around, @Aratz was finding
Nextflow.error
didn't work outside of a workflow context.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would make sense, we have to import the
Nextflow
class in the groovy files I think...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the misunderstanding.
nextflow.Nextflow.error
: Already imported into the namespace by Nextflownextflow.Nextflow
: Not in namespace, but can be manually imported if you really want to (but really, don't).nextflow
: Not in namespace, but can be manually imported if you really want to (but really, don't).For those that would prefer examples:
This will not work
Here because
Nextflow
is not in the namespace:The following will all work
Here we give the full namespace:
Here because we import Nextflow into the namespace:
The two "working" examples are only provided for pedagogical purposes. They should always be abandoned in favour of the example below, where we rely on Nextflow importing
nextflow.Nextflow.error
into namespace for us:and of course, the best and correct way:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome explanation! Thanks for going through that!
Now do you want to PR it to the official Nextflow docs or Nextflow gotchas? 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, there's always a catch. Not quite sure if there's an obvious place in the Nextflow docs. Maybe a good home would be the "Groovy imports" module in the advanced training which is currently being merged into training.nextflow.io.