Skip to content
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

A web UI bug when use Chrom and Firefox browser #2265

Closed
barnettZQG opened this Issue Dec 8, 2016 · 9 comments

Comments

Projects
None yet
7 participants
@barnettZQG
Copy link

barnettZQG commented Dec 8, 2016

Uncaught ReferenceError: Handlebars is not defined(…)(anonymous function) @ graph.js?v=1:6

This is a browser compatibility issues, so that the Graph can't display.
Safari browser no problem.

@tattsun

This comment has been minimized.

Copy link
Contributor

tattsun commented Dec 9, 2016

@barnettZQG
Could you tell me what versions of browser and prometheus did you use?

@samis

This comment has been minimized.

Copy link

samis commented Dec 9, 2016

I'm experiencing this issue too and want to provide more detail.
My client browser is Gentoo's stable Firefox 45.
As for the server Prometheus version, I am using 1.2.3+ds2-4 from the Debian repository

@arthur-c

This comment has been minimized.

Copy link

arthur-c commented Dec 11, 2016

Same problem with Chrome Version 55.0.2883.75 (64-bit) : the graph page only display "add graph" and the click is ineffective.
Ok with FF 50.0.2 and Konqueror 4.14.24

With Konqueror, I can reproduce the problem if I try to load a graph from an alert query (the URL after the IF statement) : I have an "empty" graph page.

The issue started with 1.4.0 (I rollbacked) and still present with 1.4.1

@barnettZQG

This comment has been minimized.

Copy link
Author

barnettZQG commented Dec 11, 2016

@arthur-c That's right.

@arthur-c

This comment has been minimized.

Copy link

arthur-c commented Dec 11, 2016

Humm, I am able to display the graph page on chrome after several page reloads without cache (ctrl + F5), on konqueror with simple multiple reloads

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Dec 13, 2016

We definitely saw a number of issues that could be resolved with a "hard reload" (Ctrl+Shift+R).

@brancz

This comment has been minimized.

Copy link
Member

brancz commented Dec 13, 2016

Some systems like the rails assets pipeline add hashes to the assets and avoids caching problems with that. Maybe we can do something similar, in fact I would be surprised if we're the first ones doing that.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jul 14, 2017

Sounds like this was a transient caching issue.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.