{"action":"created","issue":{"url":"https://api.github.com/repos/spotify/luigi/issues/1283","labels_url":"https://api.github.com/repos/spotify/luigi/issues/1283/labels{/name}","comments_url":"https://api.github.com/repos/spotify/luigi/issues/1283/comments","events_url":"https://api.github.com/repos/spotify/luigi/issues/1283/events","html_url":"https://github.com/spotify/luigi/issues/1283","id":110262133,"number":1283,"title":"Visualization gets messy in some cases","user":{"login":"samuell","id":125003,"avatar_url":"https://avatars.githubusercontent.com/u/125003?v=3","gravatar_id":"","url":"https://api.github.com/users/samuell","html_url":"https://github.com/samuell","followers_url":"https://api.github.com/users/samuell/followers","following_url":"https://api.github.com/users/samuell/following{/other_user}","gists_url":"https://api.github.com/users/samuell/gists{/gist_id}","starred_url":"https://api.github.com/users/samuell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samuell/subscriptions","organizations_url":"https://api.github.com/users/samuell/orgs","repos_url":"https://api.github.com/users/samuell/repos","events_url":"https://api.github.com/users/samuell/events{/privacy}","received_events_url":"https://api.github.com/users/samuell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-10-07T16:15:55Z","updated_at":"2015-10-07T16:31:44Z","closed_at":null,"body":"We have a problem that with certain dependency graph topologies, they get very very very long (on the page) ... seemingly due to how text labels are shifted to be stacked diagonally upon each other.\r\n\r\nIn our case, this seems to create a \"domino\" effect, with longer and longer connections between up/downstream stages, to the extent that it gets unreadable. See example here (this is only the \"top of the iceberg\" :P ): \r\n![image](https://cloud.githubusercontent.com/assets/125003/10343710/7145c920-6d1f-11e5-8f84-44641a126c75.png)\r\n"},"comment":{"url":"https://api.github.com/repos/spotify/luigi/issues/comments/146254067","html_url":"https://github.com/spotify/luigi/issues/1283#issuecomment-146254067","issue_url":"https://api.github.com/repos/spotify/luigi/issues/1283","id":146254067,"user":{"login":"daveFNbuck","id":2091885,"avatar_url":"https://avatars.githubusercontent.com/u/2091885?v=3","gravatar_id":"","url":"https://api.github.com/users/daveFNbuck","html_url":"https://github.com/daveFNbuck","followers_url":"https://api.github.com/users/daveFNbuck/followers","following_url":"https://api.github.com/users/daveFNbuck/following{/other_user}","gists_url":"https://api.github.com/users/daveFNbuck/gists{/gist_id}","starred_url":"https://api.github.com/users/daveFNbuck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daveFNbuck/subscriptions","organizations_url":"https://api.github.com/users/daveFNbuck/orgs","repos_url":"https://api.github.com/users/daveFNbuck/repos","events_url":"https://api.github.com/users/daveFNbuck/events{/privacy}","received_events_url":"https://api.github.com/users/daveFNbuck/received_events","type":"User","site_admin":false},"created_at":"2015-10-07T16:31:44Z","updated_at":"2015-10-07T16:31:44Z","body":"I have this problem as well, and the D3 graph doesn't help because it's way too slow on larger graphs. Filtering by status wouldn't really help in the pictured example, as the graph is all pending nodes anyway. My graphs tend to be dominated by done nodes and have a fairly pending subgraph. One thing that I think could help here is to add a depth limit to the graph. You won't be able to see everything at once, but it'll load much faster and you can always click on the nodes you're interested in to see more detail. It would be much more useful than a lot of my graphs in which 99% of the scrolling is just pages and pages of lines with no nodes."}}