Skip to content
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

Check for new withName syntax #78

Closed
apeltzer opened this issue Jul 24, 2018 · 10 comments
Closed

Check for new withName syntax #78

apeltzer opened this issue Jul 24, 2018 · 10 comments
Assignees
Labels

Comments

@apeltzer
Copy link
Member

The old syntax, e.g.

process$name

Will be replaced by

process:withName

Which currently leads to an error while linting, see here

ICGC-featureCounts> nf-core lint .                                                                                                                                               (nf-core-lint) 

                                          ,--./,-.
          ___     __   __   __   ___     /,-._.--~\
    |\ | |__  __ /  ` /  \ |__) |__         }  {
    | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                          `._,._,'
    
Running pipeline tests  [##################------------------]   50%  'check_nextflow_config'

CRITICAL: Critical error: ('`nextflow config` returned non-zero error code: %s,\n   %s', 1, b"ERROR ~ Unable to parse config file: '/home/alex/IDEA/nf-core/ICGC-featureCounts/nextflow.config'\n\n  Compile failed for sources FixedSetSources[name='/groovy/script/ScriptACEE592A55CA6E05E4ED54DBAB544DAD']. Cause: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:\n  /groovy/script/ScriptACEE592A55CA6E05E4ED54DBAB544DAD: 26: expecting '}', found ':' @ line 26, column 12.\n       .withName:fetch_encrypted_s3_url {\n                ^\n  \n  1 error\n\n\n")

INFO: Stopping tests...

INFO: ===========
 LINTING RESULTS
=================
  16 tests passed   0 tests had warnings   0 tests failed

Should we support both or just the new syntax?

@apeltzer apeltzer added the bug Something isn't working label Jul 24, 2018
@maxulysse
Copy link
Member

I vote for just the new.
But maybe put that as a warning instead of an error if it's using the old one

@ewels
Copy link
Member

ewels commented Jul 30, 2018

+1 for just supporting the new if we need to.

Note that the error there is from nextflow though, not the linting. Should probably print the newlines in that so that it's easier to read...

`nextflow config` returned non-zero error code: %s,
   %s', 1, b"ERROR ~ Unable to parse config file: '/home/alex/IDEA/nf-core/ICGC-featureCounts/nextflow.config'

  Compile failed for sources FixedSetSources[name='/groovy/script/ScriptACEE592A55CA6E05E4ED54DBAB544DAD']. Cause: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
  /groovy/script/ScriptACEE592A55CA6E05E4ED54DBAB544DAD: 26: expecting '}', found ':' @ line 26, column 12.
       .withName:fetch_encrypted_s3_url {
                ^
  
  1 error

What version of nextflow is installed? It could be that the linting itself is fine..

@apeltzer
Copy link
Member Author

apeltzer commented Jul 30, 2018

I think that was 0.30.2, now with 0.31.0 the error is gone ?!

@ewels
Copy link
Member

ewels commented Aug 2, 2018

Can we close this?

@apeltzer
Copy link
Member Author

apeltzer commented Aug 2, 2018

Yup - will do. I guess the linting is still fine :-)

@apeltzer apeltzer closed this as completed Aug 2, 2018
@ewels
Copy link
Member

ewels commented Aug 2, 2018

Though perhaps the linting should check for the new format and throw a warning / error about the old?

@ewels ewels reopened this Aug 2, 2018
@ewels ewels changed the title Support new withName syntax Check for new withName syntax Aug 2, 2018
@ewels ewels added enhancement and removed bug Something isn't working labels Aug 2, 2018
@apeltzer
Copy link
Member Author

apeltzer commented Aug 2, 2018

Agreed - I dont know when this will be not just a warning in Nextflow but an actual error message ? @pditommaso may know when this is the case ;-)

@ewels
Copy link
Member

ewels commented Aug 2, 2018

Either way, we should definitely be using the new syntax for all pipelines now.

@pditommaso
Copy link

it will stay for a while as a warning, but I agree with Phil better to switch to the new syntax also because it's more flexible.

@senthil10 senthil10 self-assigned this Aug 8, 2018
@ewels ewels added linting and removed enhancement labels Aug 8, 2018
apeltzer pushed a commit that referenced this issue Aug 9, 2018
@senthil10
Copy link
Contributor

Done in #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants