[
https://issues.apache.org/jira/browse/DISPATCH-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070939#comment-16070939
]
ASF subversion and git services commented on DISPATCH-792:
----------------------------------------------------------
Commit a5bb8051b96da65832c58311841f28835afd71e6 in qpid-dispatch's branch
refs/heads/master from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a5bb805 ]
DISPATCH-792 Fix freezing/unfreezing nodes and moving nodes on top of each other
> Freezing and moving nodes is somewhat broken (in either version of console)
> ---------------------------------------------------------------------------
>
> Key: DISPATCH-792
> URL: https://issues.apache.org/jira/browse/DISPATCH-792
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
> Affects Versions: 1.0.0
> Environment: Dispatch and Dispatch plugin at commit e22091b3
> Built without libwebsocket, used the old websockify way to connect console
> Firefox 51.0.1, Chrome 56.0.2924.87 (64-bit) on Linux
> Reporter: Jiri Danek
> Priority: Minor
>
> If I freeze a node using the right-click menu, then
> 1) The label in the popup menu randomly switches Freeze/Unfreeze and it is
> tricky to click the Unfreeze option: https://youtu.be/DwczdnMnnkc
> if I am dragging a frozen router node on top of console node, then
> 2) The legend switches to the other node. I would expect it not to change.
> https://www.youtube.com/watch?v=HSCxFvFnfTs
> 3) If I put the nodes exactly on top of each other, I get the following
> exception in browser log.
> {noformat}
> Error: <path> attribute d: Expected number, "MNaN,NaNLNaN,NaN".
> a @ d3.min.js?_=1497955959439:1
> (anonymous) @ d3.min.js?_=1497955959439:3
> Y @ d3.min.js?_=1497955959439:1
> Aa.each @ d3.min.js?_=1497955959439:3
> Aa.attr @ d3.min.js?_=1497955959439:3
> tick @ VM79:1125
> t @ d3.min.js?_=1497955959439:1
> l.tick @ d3.min.js?_=1497955959439:4
> Rn @ d3.min.js?_=1497955959439:1
> Tn @ d3.min.js?_=1497955959439:1
> {noformat}
> Issue 3 is very hard to reproduce, I was able to trigger it two times in
> hawtio version of console, and then never. Unless it can be figured out from
> code what could went wrong, it is probably not worth the time to investigate
> further.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
