Circular dependency

[Jeppesen-io]

After updating to the latest release I get a 'Circular dependency' but only sometimes, mostly on first load. It feels like a race condition. It will load my dastboard but no log data from elastic search.

I get the problem in Chrome and Firefox in Windows. Both are latest version.

Chrome:
Error: Circular dependency:
at Error ()
at c (http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:8520)
at d (http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:8748)
at Object.e as instantiate
at http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:21835
at http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:17184
at f (http://s3.int/logging/kibana/app/app.js?r=942fd2d:6:28560)
at n (http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:17049)
at f (http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:15004)
at http://s3.int/logging/kibana/app/app.js?r=942fd2d:7:14570
Firefox:
[09:51:20.036] "Error: Circular dependency:
c
@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
d@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
e@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
n/<@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
f@http://s3.int/logging/kibana/app/app.js?r=942fd2d:6
n@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
f@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
z/<@http://s3.int/logging/kibana/app/app.js?r=942fd2d:7
g@http://s3.int/logging/kibana/app/app.js?r=942fd2d:20
.link/</</<@http://s3.int/logging/kibana/app/app.js?r=942fd2d:20
a.require/</<@http://s3.int/logging/kibana/app/app.js?r=942fd2d:21
f.prototype.$eval@http://s3.int/logging/kibana/app/app.js?r=942fd2d:8
f.prototype.$apply@http://s3.int/logging/kibana/app/app.js?r=942fd2d:8
a.require/<@http://s3.int/logging/kibana/app/app.js?r=942fd2d:21
newContext/u.execCb@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.check@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.enable/</<@http://s3.int/logging/kibana/vendor/require/require.js:4
bind/<@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.emit/<@http://s3.int/logging/kibana/vendor/require/require.js:4
each@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.emit@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.check@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.enable@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/t.prototype.init@http://s3.int/logging/kibana/vendor/require/require.js:4
o@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/u.completeLoad@http://s3.int/logging/kibana/vendor/require/require.js:4
newContext/u.onScriptLoad@http://s3.int/logging/kibana/vendor/require/require.js:4
"

[rashidkpc]

Try clearing your browser cache and reloading

[Jeppesen-io]

I've done that a few times in Firefox and Chrome, no help.

[rashidkpc]

Instead of running from the built distribution, can you run from src/ in master and see if it still happens?

[Jeppesen-io]

So far using src/ in master seems to resolve my issues although it seems to load slower.

[rashidkpc]

Yeah, certainly not a solution, I was just curious if the issue occurred there in hopes we could get some better debug output

[doxavore]

I get this same error in Chrome on Linux, running 3.0.0milestone4 not embedded. For me, it seems to be random, and refreshing the page (sometimes several times) resolves it - almost like there's some indeterminate load order issue popping up randomly.

[danburke]

I also see this error in Chrome on Mac running 3.0.0milestone4.
It's also random

[rashidkpc]

Can someone export a dashboard the has been known to cause this? Its possible it is related to some specific panel

[danburke]

I have a dashboard export from when this occured, I'd prefer not to attach it here as it includes proprietary information.
The panels referenced are:

% cat Default-1383827648733.json | jq '.rows[].panels[].type'                              
"histogram"
"terms"
"query"
"derivequeries"
"table"

[rashidkpc]

From #669

Sometimes, js errors appears in console on load. It can be reproduced at http://demo.kibana.org/#/dashboard and at my local kibana in Chrome and Firefox (also, with all extensions disabled).

[Jeppesen-io]

The latest commit seems to have fixed my issue. I'll post if I see it again.

[rashidkpc]

Thanks, I'm going to leave this open for awhile because I was never able to replicate it. Feel free to update if it stays gone

[markwalkom]

Just wanted to point out we ran into this and running from current src fixed it.

[FestivalBobcats]

Yeah, I can confirm running from latest /src fixed it.

Using the latest .zip download, I ran into the circular dependency issue in both Chrome and Safari. It seems to trigger once I've hit the default.json dashboard, clicked on one of the sample dashes, closed the tab, and reopened default.json (or at that point, any route). However, it would reset after clearing browser cache.

[rashidkpc]

So you're still seeing this in the current built kibana-latest.tar.gz? Can you get a copy/paste or a screenshot?

[FestivalBobcats]

Very odd... it seems I can no longer reproduce the issue. Did you update the latest build? I was using the .zip (not the .tar.gz) just yesterday and it was still breaking. Like I said though, it didn't break immediately, just once I had moved from default.json into another dash, and then tried opening index.html again.

Not sure if it matters, but I'm running Kibana as a site plugin in Elasticsearch. Just downloading/extracting into $ES_HOME/plugins/kibana/_site.

[rashidkpc]

I did update the build, though not with anything that should've influenced this. Reproducibility has been a large blocker in fixing this one. I've seen it once, and then never again :-/

[FestivalBobcats]

Heh, diagnosing JS problems is a tough job for sure. It seemed to be related to browser cache, but aside from that I have absolutely no clue. All is good now, though!

[rashidkpc]

Please let me know if the behavior reoccurs

[rashidkpc]

Going to close this again since no one can reproduce.

[rafaelmagu]

Just so I'm clear: milestone 4 presents the problem but src/ doesn't, right?

[rashidkpc]

Correct, milestone 5 should be ok too