Alex Kanitz
Alex Kanitz
Would be very interested to have this merged, or have the issue of dealing with different content types addressed anyhow
I agree with the need for this, and I also agree with defaults being broadcast so that, e.g., one can also pull an appropriate WES from a service registry ("give...
My last point was motivated by the idea that it would be rather terrible user experience if if a client first needed to test WES instance by instance to see...
I was thinking of ranges more for specifying supported workflow type versions (rather than engine versions). The workflow types I am familiar with only have a couple of versions, but...
I was thinking of ranges more for specifying supported workflow type versions (rather than engine versions). The workflow types I am familiar with only have a couple of versions, but...
I don't even think it's worth opening an issue. We can leave that up to the first person running in to that problem :)
Hi @patmagee, unfortunately I'm not on top of my GitHub notifications at all and didn't see your answer. They are all excellent points! I think we have thought about all...
While I can well imagine that being able to use private container images is an important use case particularly in industry settings, I find uploading large files via workflow attachments...
> @mr-c would an alternative solution be for the specific Wes engine to provide information on what container registries it supports (similar to supported file types) or maybe even as...
Tagging @denis-yuen and @coverbeck here