-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
TypeError: e is undefined #28120
Comments
@Berbe so the issues you have referenced is due to a different reason. I can see why you could think that they are related due to the error message but that is somewhat a standard error. However the error you have posted has to do with the parsing of the URL. Could you share how the query string looks for your dashboard that crashes? That would help us resolve this. |
Thanks for this piece of information. For all the following errors, the URL was
Crash
Crash 1
Crash 2
|
Could you share a copy of your dashboard json? Just so I can see what template variables you have setup? |
I am a bit unsettled about giving out potentially sensitive data. Here is that share (removed). |
You seem to have a data link that is causing this, need the panel json for the panel in order to replicate this |
Share (removed) (1d expiration) I noticed some errors happened when I tried to update the template variables. In particular, I noticed requests to |
@Berbe thanks for reporting this! I have opened a fix for this. |
What happened:
TypeError
errors pop up in console, sometimes making a Dashboard crash.No error spawned by the server run with a
debug
log level: definitely seems like a frontend error bug.Error displayed when a Dashboard crashes
Examples of console error on Dashboard crash
Crash 1
Crash 2
Example of console error while Dashboard did _not_ crash
What you expected to happen:
No error, no crash
How to reproduce it (as minimally and precisely as possible):
Fiddling with template variables in order to make a Dashboard refresh, sometimes not doing anything other than hovering over Panels.
Anything else we need to know?:
Other potentially related issues
v6.6.1
Error already encountered with v6.6.1
Console error v6.6.1
Environment:
The text was updated successfully, but these errors were encountered: