Nextflow community chat moved to Slack! https://www.nextflow.io/blog/2022/nextflow-is-moving-to-slack.html
pditommaso on master
Add errorStrategy validation S… (compare)
pditommaso on fusion-tags
Add support for fusion tags Si… (compare)
pditommaso on master
Add Fusion integration test Si… (compare)
jordeu on wave-debug-remote
Add support for debuging a Fusi… (compare)
pditommaso on master
Add Wave tests Signed-off-by: … (compare)
pditommaso on master
Improve K8s securityContext sup… (compare)
cat test.nf
Channel.fromPath("/home/lindenb/src/jvarkit-git/src/test/resources/toy.bam").
splitSamples().
dump()
$ ./nextflow run test.nf
N E X T F L O W ~ version 19.08.0-SNAPSHOT
Launching `test.nf` [goofy_goldstine] - revision: f56eb762e4
Unknown method `splitSamples` on channel type
Hello guys. I'm trying to run nextflow with Kubernetes and have encountered some sort of problem with non-root user. Nextflow was trying to initialise a Pod but got an exception of "container init caused \"mkdir /mnt/tvu: permission denied". Below is the Kubernetes manifest generated by nextflow:
apiVersion: v1
kind: Pod
metadata:
name: nf-68b883e7affa9dc5d6d5e721c75b21c4
namespace: default
labels: {app: nextflow, runName: sleepy-goodall, taskName: indexPeptides, processName: indexPeptides,
sessionId: uuid-0e5b6c81-4527-4213-a9ba-16e40e424220}
spec:
restartPolicy: Never
containers:
- name: nf-68b883e7affa9dc5d6d5e721c75b21c4
image: omicsdi/crux:latest
command: [/bin/bash, -ue, .command.run]
workingDir: /mnt/tvu/work/68/b883e7affa9dc5d6d5e721c75b21c4
volumeMounts:
- {name: vol-1, mountPath: /mnt}
securityContext: {runAsUser: 2801}
volumes:
- name: vol-1
persistentVolumeClaim: {claimName: pride-pv-claim}
I have assigned rw permission to the persistent volume. When I removed the workingDir, the pod was started successfully and I was be able to cd into the /mnt/tvu/work/68/b883e7affa9dc5d6d5e721c75b21c4 folder. So, I suspect that the runAsUser and workingDir couldn't get along.
Is there anyone have experienced this issue?
WARN: The channel
createmethod is deprecated -- it will be removed in a future release
when I use the Channel.create()
method, but I find nowhere any mention of what's replacing it. Is the warning wrong or is there some undocumented feature I'm missing?
ch_input = Channel.create()
@pditommaso
this is just great, isn't it ?
https://twitter.com/yokofakun/status/1159468857934929922
Confirmed, this is great
https://gitter.im/nextflow-io/nextflow?at=5d4802a1475c0a0feb021c1b
Could you give us a few examples @pditommaso to illustrate this point? It still feels a bit abstract without a few concrete examples
Channel.fromMap("my.bam").flatMap(Htsjdk::extractSamples)
fatal error: An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied
when trying to run a pipeline on AWS Batch. Pretty sure it's due to the s3 access of the workDir but I've double checked and I am the owner of that bucket. Any ideas?
A question regarding input of memory specifications. Using the config
params {
memParam = 7.GB
}
process {
withName:sayHello {
memory = {2 * params.memParam}
}
}
works fine when memParam
is not used, but when it is: nextflow run main.nf -c base.conf --memParam 8.GB
, I get either
ERROR ~ Error executing process > 'sayHello (3)'
Caused by:
No signature of method: java.lang.Integer.multiply() is applicable for argument types: (java.lang.String) values: [8.GB]
Possible solutions: multiply(java.lang.Character), multiply(java.lang.Number)
or
Error executing process > 'sayHello (1)'
Caused by:
Not a valid 'memory' value in process definition: 8.GB8.GB
depending on the order of the multiplication. What am I missing? (I'm on Nextflow version 19.04.1 build 5072)
unable to resolve class nextflow.util.MemUnit