Hi - Yes, this is still happening. Clearing my browser's cache didn't
help. I suspect this is related to a tool being removed/renamed that is
used in the workflow, but not completely sure. Attached is the exported
workflow.
Let me know if you need anything else to help debug this. Thanks,
Ry
Ryan - is this still a problem? I assume there is some use of dataset
collections in this workflow? What would be ideal is to determine a
minimum combination of data flow (connections) and tools that exhibit
this - and then share that workflow and tool with me. If you don't
have time for that - may
Just a quick general suggestion: have you tried clearing your browser cache?
Thanks for using Galaxy,
Dan
On Jul 15, 2015, at 11:18 AM, Ryan G wrote:
> The error I see is "TypeError: c.effectiveMapOver is not a function" in
> static/scripts/galaxy.workflow_editor.canvas.js?v=1436897004
>
The error I see is "TypeError: c.effectiveMapOver is not a function" in
static/scripts/galaxy.workflow_editor.canvas.js?v=1436897004
On Tue, Jul 14, 2015 at 4:50 PM, Björn Grüning
wrote:
> Hi Ryan,
>
> try to look at the JS console. I suspect some problem with one of the
> tools in your workflow
Hi Ryan,
try to look at the JS console. I suspect some problem with one of the
tools in your workflow.
Cheers,
Bjoern
Am 14.07.2015 um 22:02 schrieb Ryan G:
> Hmmm this only happens on a specific workflow. How can I debug this?
>
> On Tue, Jul 14, 2015 at 3:37 PM, Ryan G wrote:
>
>> It looks
Hmmm this only happens on a specific workflow. How can I debug this?
On Tue, Jul 14, 2015 at 3:37 PM, Ryan G wrote:
> It looks like a recent commit since 6/26 to 15.05 is break the workflow
> editor. I have a pipeline I'm trying to edit. I updated my instance of
> Galaxy and now when I try to
It looks like a recent commit since 6/26 to 15.05 is break the workflow
editor. I have a pipeline I'm trying to edit. I updated my instance of
Galaxy and now when I try to edit a workflow, the editor is stuck at
"Loading workflow editor".
__
