elasticsearch

For the JarHell Bootstrap Check, a user is seeing the following:

java.lang.IllegalStateException: failed to load plugin x-pack-core due to jar hell
at org.elasticsearch.plugins.PluginsService.checkBundleJarHell(PluginsService.java:524) ~[elasticsearch-7.6.2.jar:7.6.2]
at org.elasticsearch.plugins.PluginsService.loadBundl

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Kibana version: 7.14.0

Browser version: Chrome latest

Browser OS version: OS X

Describe the bug: Can we either display a tooltip or remove the "include related objects" option from the copy saved objects between spaces UI. Its permanently checked and greyed out now and that's confusing as an user.

<img width="1792" alt="Screen Shot 2021-07-27 at 5 59 35 PM" src="http

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}