Conversation
This should fix galaxyproject#719.
|
Cool - thanks @mvdbeek - I'll work on getting a release out with this in it. |
|
Shouldn't that be fixed upstream in cwltool? |
|
Perfect, thanks @jmchilton! |
|
@nsoranzo Cool - thanks! I've made that change in #714 and rebased it as d2ea830. I'm going to see what the tests say about #723 and if things look okay I think I will do a release so this is fixed and Conda is fixed as well. Then I will merge #714 later this week (or maybe later today) and create a new set of problems. |
|
Well so things went sideways because the new galaxy-lib introduced test errors (these can be seen in #723 but would be experienced in the wild anyway since we don't pin an upper bound on galaxy-lib). So I just cleaned up and merged my CWL WIP with 2462099 and did a release so either the dependencies are fixed when coming from PyPI ... hopefully ... but probably not and we shall see. |
|
@jmchilton I couldn't see any new test error in https://travis-ci.org/galaxyproject/planemo/jobs/272496388:
Am I missing something? |
|
I just hadn't seen the jobloaderctx error previously - my 👀 aren't 🦅 (they call me 💩👀). I didn't think it would have occurred with older galaxy-libs before the two I released today. |
|
jobloaderctx error is a side-effect of pinning ruamel.yaml in this very PR, in fact it started with https://travis-ci.org/galaxyproject/planemo/jobs/272481174 |
This should fix #719.