Hello Galaxy Developers, I have a user who noticed a potential bug when extracting workflows from histories on our local Galaxy server. I have recreated the bug on the public Galaxy server with a much smaller history. The history can be found here: http://main.g2.bx.psu.edu/u/jmchilton/h/column-join-workflow-bug Basically when creating workflows from such histories, the second input to "Column Join" never seems to be connected to the previous step the way I would expect it to be. In the workflow editor you can manually create this connection, but it is easy to miss this in a large worfklow and have incomplete results as a consequence. Am I missing something or is this a bug? Thanks for your time, -John
John, I took a look at this and it's definitely a defect, not something you're missing. Thanks for the report, I can let you know when a fix is available. -Dannon On Jul 28, 2011, at 2:30 PM, John Chilton wrote:
Hello Galaxy Developers,
I have a user who noticed a potential bug when extracting workflows from histories on our local Galaxy server. I have recreated the bug on the public Galaxy server with a much smaller history. The history can be found here: http://main.g2.bx.psu.edu/u/jmchilton/h/column-join-workflow-bug
Basically when creating workflows from such histories, the second input to "Column Join" never seems to be connected to the previous step the way I would expect it to be. In the workflow editor you can manually create this connection, but it is easy to miss this in a large worfklow and have incomplete results as a consequence. Am I missing something or is this a bug?
Thanks for your time, -John <workflow_from_history.png>___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Dannon Baker
-
John Chilton