Jeff Gentry
Jeff Gentry
I agree that this would be a very good idea. That said it is unlikely to happen in the near future. @antonkulaga If this is something you've managed to work...
@chunjie-sam-liu Did you wind up being able to resolve this?
@likeanowl In server mode, it's just part of the [API request](https://github.com/broadinstitute/cromwell/blob/develop/engine/src/main/resources/swagger/cromwell.yaml#L65).
@likeanowl Yes - you just need to specify it in the centaur [test description](https://github.com/broadinstitute/cromwell/blob/develop/centaur/src/main/resources/standardTestCases/docker_alpine.test#L8), with a pointer to where the option file lives
@caaespin I'm assuming that means you still see this. Are you using a recent Cromwell version? (42+)
@alexwaldrop NB that I don't work there anymore and sadly haven't had the energy to actively contribute. Perhaps @aednichols can chime in
@whlavina I don't think I agree that because many batch schedulers do a thing that a workflow description should do that thing. IMO that's up to the implementation to decide....
As a representative of one of the CWL implementations, I feel your pain - I find the status quo to be extremely limiting. The stock answer is that it's up...
> In WDL, there's call-caching which seems homologous to workreuse, but I don't see anything similar for the debugging use case I am proposing. To be clear, WDL does not...
I'm good w/ this