Jordi Deu-Pons

I like the idea. Another approach could be that Tower generates an open but secret URL that gives all this information taking care of anonymizing everything (paths, IPs, random strings...)...

We have an error here, but it's not related with the parser it self. The problem is that only the profiles at master are used to do this checking, so...

@apeltzer notice that, even if Tower Agent can be used in a future as a connection gateway, right now at Tower side you can only use it to submit jobs...

> So I need to have a Tower Version that can work with the Tower Agent, the "fake Slurm" part above on the machine running the jobs and then should...

Given this `main.nf`: ``` #!/usr/bin/env nextflow cheers = Channel.from 'Bonjour', 'Ciao', 'Hello', 'Hola' process sayHello { echo true input: val x from cheers script: """ echo '$x world! CPUS:${task.cpus}' """...

I'm also affected. I've a workaround. Define a function like this in your parent: ``` function myswal(value) { v = {}; for (var key in value) { v[key] = value[key];...

> Not sure it's a good idea, why doing this? What do you mean? my comment or the whole thing?

The root of the problem is that here the CLI wants to do an exact match search by pipeline name because we expect the name to be unique. And the...

> I see; therefore, it's the field in the request. As such, should not be managed on BE side? how the FE handle this? The FE do not has this...

What is the "the workflow publish"?