These are chat archives for nextflow-io/nextflow
#!/usr/bin/env nextflow. Why does something like
bashis in the shebang rather than
nextflow run myscript.nfwhich overrides the shebang interpreter. Not super important, I was just curious.
nextflow run myscript.nf... the kernel never sees the shebang line, but nextflow does.
-w(and using the
runOptions = '-B /some/path'settings in the
.command.run. At this point, as far as I understand (? not sure...) I'm in a no-man's-land: the job is always in state SUBMITTED and nextflow doesn'invoke
queueStatusCommandthat would show him that the job is in state FAILED. Could it be possible ? How/where could I ask nextflow to force to have a look at the job status ? Thanks.