Irvin Zhan
Irvin Zhan
Confirmed here as well. Any workaround for Kibana 4 would be appreciated!
ah yes, my fork you mentioned used a reverse proxy built in express to workaround this. there are a few more commits that aren't pushed up to that fork that...
Hard to say! Another possible fix would be to add the line `ruby '1.9.3'` to the Gemfile to specify the Ruby version. Not sure though...would be worth investigating the gem...
@mx2323 I haven't tested it yet, but after calling `layout()`, take the output ordering of nodes within the same rank (done by looking at their x + y coordinates) and...
@branpk ah good point, this won't necessarily solve outgoing edges. My understanding is that this PR fixes the second ask of #112 (within same rank): > In fact, it would...
I found it helpful to follow https://github.com/dagrejs/dagre/wiki#an-example-layout To configure layout options, pass the a config object to `setGraph` e.g. ```js g.setGraph({rankdir: "LR", ranker: "network-simplex", align: "UL" }); ```
@Anislav Awesome, thanks for the feedback. That's the same workaround we are using right now.
+1 encountering this issue on my end as well when using a Redis Notification Feed @jquacinella what was your solution in the end?
@jquacinella if you are using a Redis store and Python 2, have you tried the fix I proposed in https://github.com/tschellenbach/Stream-Framework/issues/147? Let me know if that works for you! :)
indeed, it's an unlikely edge case, but this will break for any existing activities that serializes into a string that ends with a backslash.