Message: "q.range is undefined" when launching scripted dashboard

I’m getting the following stack in my console:

TypeError: q.range is undefined
Stack trace:
m@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:7:188788
c@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:7:188156
link/<@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:7:192278
o.prototype.emit@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:15:521176
i</t.prototype.emit@http://grafana.staged-by-discourse.com/public/build/app.bfd9f650a928040b5eed.js:1:11343
[1309]/h</t.prototype.render@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:1:17598
[1478]/h</e.prototype.onDataError@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:7:182219
o.prototype.emit@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:15:520746
i</t.prototype.emit@http://grafana.staged-by-discourse.com/public/build/app.bfd9f650a928040b5eed.js:1:11343
[1422]/f</e.prototype.onMetricsPanelRefresh/<@http://grafana.staged-by-discourse.com/public/build/0.fa4858d56219f67b75eb.js:7:17221
u@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:68722
l/<@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:69127
$digest@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:74824
$apply@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:76636
o/c<@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:84010
i@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:21868
me/l.defer/n<@http://grafana.staged-by-discourse.com/public/build/vendor.fc5441def755e2a9f98e.js:43:23332

It says it’s reporting from angular.js:14700 which has the comment:

// Support: IE 9 only
// console methods don't inherit from Function.prototype in IE 9 so we can't
// call `logFn.apply(console, args)` directly
    return Function.prototype.apply.call(logFn, console, args);

Should I be concerned about this being spit out in firefox/chrome and if so, how should I go about troubleshooting?

Please, post you scripted dash.