-
Notifications
You must be signed in to change notification settings - Fork 42
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
Posible fix for issue #127 #128
Conversation
Dev -> master with subway fixes
Dev -> master for v1.1.1
Dev -> master for v1.2.0
|
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.
Looks sensible- thanks for the fix!
I’d normally object to lots of random spacing changes unrelated to the fix (presumably from your IDE), but it mostly seems to be rogue spaces being removed (@WackerO will be happy), and it’s come up before, so we’ll allow it ;-).
Ahh, wait, @ctuni - could you add the file existence check before you merge? |
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.
Just need a file existence check
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.
Just need a file existence check
HI! I'm sorry for the IDE and whitespaces thing, I did not realized it happened when pulling. I can try and re-do the PR with it but thanks for allowing it! I added the file existence check also :) |
No, don’t worry, @WackerO had the same issue before, and the changes are harmless. Thanks for the fix. |
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.
LGTM now
Well this is brilliant :D I was asking Cris to remove the whitespaces because I sensed a disturbance in the force and predicted your objection, @pinin4fjords! But yes, I am happy ^^ |
#127 This is a possible fix for the aforementioned issue. I tested both with
-profile test,docker
and with my data and infrastructure and the process that was failing on my case (VALIDATOR
) is no longer failing. Thetest
profile was not failing but it's working correctly with the fix also.The change is made in the creation of
ch_input
channel, just addingfile()
aroundparams.input
. Apparently, this way the input matrix can be read as a file and it does not throw the error.This change is made in line 17 of
differentialabundance.nf
file.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).