Support Kibana 6.3.0

[v01t]

Support Kibana 6.3.0

[v01t]

Hi,

Browser console error (Discover):

TypeError: Expected private module "undefined" to be a function
    at identify (commons.bundle.js:3)
    at Private (commons.bundle.js:3)
    at Object.NetworkVisTypeProvider (commons.bundle.js:3)
    at Object.invoke (vendors.bundle.js:133)
    at instantiate (commons.bundle.js:3)
    at get (commons.bundle.js:3)
    at Private (commons.bundle.js:3)
    at Array.map (<anonymous>)
    at Object.registry (commons.bundle.js:3)
    at Object.invoke (vendors.bundle.js:133)
    at instantiate (commons.bundle.js:3)
    at get (commons.bundle.js:3)
    at Private (commons.bundle.js:3)
    at Object.VisProvider (commons.bundle.js:3)
    at Object.invoke (vendors.bundle.js:133)
    at instantiate (commons.bundle.js:3) "<div class="application" ng-class="'tab-' + chrome.getFirstPathSegment() + ' ' + chrome.getApplicationClasses()" ng-view="" ng-controller="chrome.$$rootControllerConstruct as kibana">"

Browser console error (Visualize):

Error: Circular reference to "VisProvider" found while resolving private deps: VisProvider -> registry -> NetworkVisTypeProvider -> registry -> function(savedVisualizations){return savedVisualizations}
    at instantiate (commons.bundle.js:3)
    at get (commons.bundle.js:3)
    at Private (commons.bundle.js:3)
    at Object.<anonymous> (commons.bundle.js:3)
    at Object.invoke (vendors.bundle.js:133)
    at Object.$get (vendors.bundle.js:133)
    at Object.invoke (vendors.bundle.js:133)
    at vendors.bundle.js:133
    at getService (vendors.bundle.js:133)
    at injectionArgs (vendors.bundle.js:133)
    at Object.instantiate (vendors.bundle.js:133)
    at Object.<anonymous> (vendors.bundle.js:133)
    at Object.invoke (vendors.bundle.js:133)
    at Object.$get (vendors.bundle.js:133)
    at Object.invoke (vendors.bundle.js:133)
    at vendors.bundle.js:133 "<div class="application" ng-class="'tab-' + chrome.getFirstPathSegment() + ' ' + chrome.getApplicationClasses()" ng-view="" ng-controller="chrome.$$rootControllerConstruct as kibana">"

Browser console error (Dashboard):

Error: Circular reference to "registry" found while resolving private deps: VisProvider -> registry -> NetworkVisTypeProvider -> registry -> function(savedVisualizations){return savedVisualizations}
    at instantiate (commons.bundle.js:3)
    at get (commons.bundle.js:3)
    at Private (commons.bundle.js:3)
    at new DashboardListingController (commons.bundle.js:3)
    at Object.instantiate (vendors.bundle.js:133)
    at vendors.bundle.js:133
    at Object.link (vendors.bundle.js:159)
    at vendors.bundle.js:133
    at invokeLinkFn (vendors.bundle.js:133)
    at nodeLinkFn (vendors.bundle.js:133)
    at compositeLinkFn (vendors.bundle.js:133)
    at vendors.bundle.js:133
    at vendors.bundle.js:133
    at boundTranscludeFn (vendors.bundle.js:133)
    at controllersBoundTransclude (vendors.bundle.js:133)
    at update (vendors.bundle.js:159) "<div class="application" ng-class="'tab-' + chrome.getFirstPathSegment() + ' ' + chrome.getApplicationClasses()" ng-view="" ng-controller="chrome.$$rootControllerConstruct as kibana">"

Kibana logs

Thanks.

[lmangani]

@v01t yes, working on the required changes in the spare time, so it should become available in the coming weeks, unless anyone else reading this is willing to contribute and accelerate the process ;)

[lmangani]

@v01t if you're willing to test and provide feedback you can run the following command and attempt installing - mind this might produce errors we can then fix in this thread:

VERSION="6.3.0" ./release.sh

[v01t]

@lmangani thanks, I did a test, unfortunately, release.sh didn't work for me but I replace version manually in package.json and build in the same way as a release.sh do.

Kibana was started with a plugin but the future usage of Kibana was completely broken, here is an example how discovery tab looks after start:

Most likelly its because of kibana changes that were introduced in 6.3.0 as I have similar bahavior for others 6.2.4 third-party plugins.

Im not an expert in nodejs but I willing to help you to test if required.

[lmangani]

Hi, this was expected to fail, but what we really need are the error messages from your browser console and from the kibana console, if possible, to get a sense of how many things have broken and confirm local testing. Thanks!

[lmangani]

Looks like it's going to be a long summer :) Thanks for the input, we'll try get this working soon!