Bruno Renié
Bruno Renié
Current master returns tracebacks in the HTTP response in case of app errors. Can you give it a try?
Cool, graphite-api 1.1 was just released and it contains that change.
@swissdave did you have the opportunity to try a newer version?
Can you provide the full graph URL?
@sgran thanks! That looks like something that should be fixed in cyanite directly… We'll have a look with @pyr.
@sgran there might be some misalignment between the (start, end, step) info and the number of datapoints passed (see zip_longest above your change). Do you still see this regularly? Can...
That makes sense. And [the commit adding kwargs support](https://github.com/graphite-project/graphite-web/commit/b776c6d42177c09e29fb191a2803300a79922608) made it to graphite-web master and not 0.9.x. @Dieterbe which version of graphite-web did you use? Your query should also fail...
@hryamzik which version of cyanite do you have? I tried the same queries on my cyanite setup (pip versions of graphite-api and cyanite, pyr/cyanite master) and couldn't reproduce the issue.
Ok. If I can have access to a setup that reproduces the issue it'd be great… I won't be available this weekend though.
The implementation makes sequential calls, which is probably going to introduce a pretty significant performance hit… We'd need to discuss this with @pyr but ideally these calls to cyanite should...