-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard share link does not load #398
Comments
An update on this: This issue occurs in a dashboard that contains a graph with seemingly no query results. For example: This is a bit strange since the graph shows up in a dashboard fine. e.g.: https://sql.telemetry.mozilla.org/dashboard/experimenter-dashboard-activity-stream-57-beta-two-rows-emtwo in the dashboard Still need some more digging to see why the query results are available for a dashboard but not in a query link and also why this affects the public URL |
@emtwo What data source is query 53639 supposed to run against? |
@alison985 It's running with Athena |
I can't reproduce "a graph with seemingly no query results" locally on either Mozilla's fork or the upstream repo. I also can't reproduce it on STMO anymore because I went to the query page and clicked Execute, so it is now giving results on the query specific page. |
Closing since we can't reproduce this for now. |
Create a dashboard, dashboard loads correctly
Get the publicly shareable secret URL
Load the public URL
See the following:
Error: "It seems like we encountered an error. Try refreshing this page or contact your administrator."
thttps://sql.telemetry.mozilla.org/static/app.edfd454ada0cc65fb718.js:1:3875thttps://sql.telemetry.mozilla.org/static/app.edfd454ada0cc65fb718.js:1:3751ehttps://sql.telemetry.mozilla.org/static/app.edfd454ada0cc65fb718.js:1:79869broadcasthttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:76482fhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:47:2135shttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:67446lhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:67618evalhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:75097digesthttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:73566applyhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:75382lhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:49606bhttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:51737khttps://sql.telemetry.mozilla.org/static/vendor.6c83a55a91d9a0c92475.js:37:52265 app.edfd454ada0cc65fb718.js:1:12709
value
https://sql.telemetry.mozilla.org/static/app.edfd454ada0cc65fb718.js:1:12709
s/</<
index.js:83:4
$broadcast
angular.js:18322
f/<
angular-route.js:657
s
angular.js:16696
l/<
angular.js:16712:25
$eval
angular.js:17994
$digest
angular.js:17808
$apply
angular.js:18102
l
angular.js:12082
b
angular.js:12291
k
angular.js:12229
The text was updated successfully, but these errors were encountered: