Closed adamrtalbot closed 6 months ago
Related https://github.com/seqeralabs/QuickLaunch-II/issues/13 and https://github.com/seqeralabs/tower-cli/issues/397
If the tower CLI encounters the bug described in https://github.com/seqeralabs/tower-cli/issues/397, seqerakit just ignores it and continues. It should raise the error properly.
Method to reproduce:
> seqerakit ./seqerakit/launch/nf-core-* DEBUG:root: Running command: tw launch --name nf-core-atacseq-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-atacseq --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmp7fhxw4mm.yaml DEBUG:root: Running command: tw launch --name nf-core-demultiplex-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-demultiplex --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmpw7cgrcun.yaml DEBUG:root: Running command: tw launch --name nf-core-rnaseq-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-rnaseq --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmpjfs88ekv.yaml DEBUG:root: Running command: tw launch --name nf-core-sarek-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-sarek --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmpzaz2ohs4.yaml DEBUG:root: Running command: tw launch --name nf-core-scrnaseq-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-scrnaseq --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmpmiv2i2ns.yaml DEBUG:root: Running command: tw launch --name nf-core-viralrecon-$TIME --workspace $SEQERA_ORGANIZATION_NAME/$SEQERA_WORKSPACE_NAME --profile $PIPELINE_PROFILE --labels profile_$PIPELINE_PROFILE --pre-run ./seqerakit/pipelines/pre_run.txt --config ./seqerakit/pipelines/nextflow_config.txt nf-core-viralrecon --params-file /var/folders/bl/mbfv_v454691rk74_cpk7m840000gn/T/tmpsl2y4xy_.yaml
Fixed in #136, thanks Adam!
Related https://github.com/seqeralabs/QuickLaunch-II/issues/13 and https://github.com/seqeralabs/tower-cli/issues/397
If the tower CLI encounters the bug described in https://github.com/seqeralabs/tower-cli/issues/397, seqerakit just ignores it and continues. It should raise the error properly.
Method to reproduce: