I'm seeing the same behavior with 1.611. Symptoms include the arrows not displaying correctly, but also very long delay in loading the view. That's probably because of the large number of JS errors related to jquery.isPlumb:
Error: Invalid value for <svg> attribute width="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute height="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="M 53,51 L 78 51 L 77 51 M 78 51 L 78 NaN L 78 NaN M 78 NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1f @ jquery.jsPlumb-1.3.16-all-min.js:1_paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="MNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1draw @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute width="NaN"
...
Prioritization is up to you guys, of course, but I don't think this is a Minor priority thing. If it were just display, I could understand. But we've also seen that loading the view pegs the CPU on our build box. That's more of an issue, I believe.
I'm seeing the same behavior with 1.611. Symptoms include the arrows not displaying correctly, but also very long delay in loading the view. That's probably because of the large number of JS errors related to jquery.isPlumb:
Error: Invalid value for <svg> attribute width="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute height="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="M 53,51 L 78 51 L 77 51 M 78 51 L 78 NaN L 78 NaN M 78 NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1f @ jquery.jsPlumb-1.3.16-all-min.js:1_paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <path> attribute d="MNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1draw @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713
jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for <svg> attribute width="NaN"
...
Prioritization is up to you guys, of course, but I don't think this is a Minor priority thing. If it were just display, I could understand. But we've also seen that loading the view pegs the CPU on our build box. That's more of an issue, I believe.