-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Firefox fatals on discover JSON view #3610
Comments
I'm able to replicate this, is it causing any observable problems for you beyond the console log message? |
Thx. The error is displayed in the UI. I would need to check logs... and browser console. I guess it's a missing vendor js file, I could check it tomorrow in the office. |
|
Yes. I can't change dashboard, visalisations, queries in the Object editor (e.. #/settings/objects/savedDashboards/SYSLOG). But the visual editing e.g. on menu entry "Visualize" works. |
What browser is this in? Chrome does not display the message, it appears in the console but there are no side effects. |
Firefox 37 on Mac OS X. might give u access when you send pm on twitter @seti321 |
Confirm too. Linux x64/Firefox 37.0.1. Cannot edit "manage searches" with the same output. Even more, I cannot directly catch "manage searches" link as mouse looks like in select mode instead of mouse with pointing finger. You can anyway click it at the border of the surrounding rectangle. |
I have the same issue when I click on settings |
Confirmed on Windows Firefox 38.0. I see a brief flash of an "edit visualization object" error page and then the whole UI reloads to this error message. One of my visualisations was corrupt due to an elasticsearch field name change but using Chrome is a valid (albeit undesirable) workaround for the time being. PS: I'm new to the entire ELK stack - having fun so far. Once I got past this bug the fix was nice and easy using an inline JSON editor. I had feared having to poke inside the docker image to change a config file but very pleased to find a nice browser GUI instead. Thanks for all your work on it! |
Definitely fatals in firefox, possibly only in the build? |
Added the 4.0.3 label back - I think this was caused by an update to |
#3960 fixes the issue for now, but it doesn't properly solve the decency resolution in the ace editor. That is, if ace's dependencies change in the future (say, if we want to support another format besides just JSON), this problem will pop up again. We should be able to copy the whole worker path into the build's public path, but we need a way to set the |
Here as well.... |
Hi, This is only in FireFox 38. In my Chromium is erverything ok. regards |
Issue is still there using kibana 4.1.2. Script file not found: worker-json.js (:0) Firefox 40.0.3 |
I see we've gone from 4.1.1 to 4.1.2, and still this issue persists. Still more reason why I'm glad I have stayed with Kibana 3. |
Got the issue too with 4.1.2 Firefox 41.0 |
Seems to be the permission of the file kibana-4.1.2-linux-x64/src/public/worker-json.js it's read only by root on my server. Changing it so it can be read seems to fix things. |
@choffee thanks the file was using mode 500 . We did a chmod a+r and now it works ! |
Confirmed running from the source. Why is this issue closed? KIBANA_VERSION='4.1.2';
KIBANA_BUILD_NUM='7562';
KIBANA_COMMIT_SHA='34af16e285598b21b9449a3e57560c89b0d11eb8'; |
+1 |
Guys, this issue is not fixed. Several people have confirmed it, and there is even a fix. How can this be closed? |
This is fixed with: Please close this issue. regards |
So we need a new release. |
Any reason not to release this? |
FWIW, this may not be completely fixed by #4969. I see a similar problem in FF running kibana:latest (4.1.2) in docker. Clicking any message triangle in the Discover view throws a similar error: Error: Script file not found: worker-json.js (:0) Error: Error: Script file not found: worker-json.js (:0) (http://192.168.99.100:5601/index.js?_b=7562:46032) and adding a |
@ghlynch try clearing your browser cache, I saw the problem persist after modifying the Dockerfile and then it resolved after I cleared my cache. The fix isn't included in 4.1.2. |
Yep, that helped. So the docker workaround above works. Thanks. |
An odd aspect of this is it appears Kibana was responding with a 304 Not Modified for worker-json.js when the content was in fact different. |
Thanks for the info on this - fixed here (Kibana 4.1.2) without having to clear browser cache by first chmod 644 worker-json.js followed by adding a blank line at the top of that file so that the contents have (slightly) changed. |
Hi,
I get this error:
using Kibana 4.0.2-linux-64, when I navigate to "manage dashboards" and click to one of the dashboards or queries. Please note dashboards have been created using 4.0.1.
A google search find some things about JSON-Editor, but not very helpful.
The text was updated successfully, but these errors were encountered: