Jeremy

Any more thoughts/progress on this? I think ristretto is a promising avenue...

I was able to kill the script in Firefox and see it is related to the applyLogScale() - ``` Error: Script terminated by timeout at: applyLogScale@http://localhost:3000/public/app/plugins/panel/graph/graph.js?bust=1493867991646:542:50 configureAxisOptions@http://localhost:3000/public/app/plugins/panel/graph/graph.js?bust=1493867991646:487:29 render_panel@http://localhost:3000/public/app/plugins/panel/graph/graph.js?bust=1493867991646:349:29 link/

I see the error details in the alert. Maybe this issue was raised before the alert existed? Or are you looking for more detail? 

I think some of the dependencies may also be removed after updating grunt, as some of these warnings are transitive dependencies.

Updated dependencies. These are the only warnings now - jdbranham@spectre:~/go/src/github.com/grafana/grafana/data/plugins/worldping-app$ npm install npm WARN prefer global [email protected] should be installed with -g npm WARN prefer global [email protected] should be installed...

unless we want to change the build script process, we can ignore these.

https://github.com/raintank/worldping-app/tree/dependency-updates

We may need to clear the CI cache - npm ERR! peerinvalid Peer [email protected] wants grunt@~0.4.1 grunt-execute should no longer be in the dependency list.

Is there a way for me to reproduce this? I'm not seeing the same behavior while testing locally. Also, which branch and browser was used?

I used Chromium and it worked ok. The 'validateCert' was checked by default when the new endpoint was discovered, even though the HTTPS check was not enabled. I enabled the...