* fix metrics field name (stats)
* add state info
* add module name count
* use a set for the unique hosts instead of a map
* fix getting beats_state info
* fix unit test
* processBeatsStatsResults and processBeatsStateResults
* Capitalize the license type in monitoring
* Revert "Capitalize the license type in monitoring"
This reverts commit 38ad3a516d.
* Pass in the type capitalized
* Revert "Pass in the type capitalized"
This reverts commit 6a05bb12f3.
* Capitalize type in license status directly so consumers do not need to worry about it
* Added coverage around search and dashboard tests.
* Added tests to check for whether the resource is available. If not, return 404.
* Skipped two tests due to https://github.com/elastic/kibana/issues/19713. Added error handling for relationships API for when no result is found. Return 404.
* Applied patch file per PR.
* Applied Chris patch and tested locally. No failures.
* Removed ajv and utilised joi for schema validation.
* Fixed package.json.
* Copied package.json description from master.
* Reverted package.json and made proper edit.
* Adding fontSize from variables
* SectionHeader style added
* Adding section headers
Needed titling for DB statement and Stacktrace on the page
* Pluralization
* Adding fontSize variable
* Creating new header title style
* Moving title into Stacktrace container
* Updated snapshots
* move unsetLogic into react component
* remove extra comment
* add comment about why empty state is needed for InputRange component
* fix broken jest test
* move empty state logic from react component to ListControl class, add comments about reset and clear functions
* add comments about clear and reset to control class
* calculate hasChanged to avoid bug where clear form still shows 'cancel changes' as active for an empty form
* use hasValue in range control to check if value exists
* add unit test for list_control_factory and cleanup range_control from review comments
* unskip reporting tests
* Focus only on flaky test suite and run 10x
* Revert "Focus only on flaky test suite and run 10x"
This reverts commit a6616b1140c29d8d3f13666d20ae94db9a97267f.
* refactor login page check, turn off telemetry
* significant refactor of navigateTo
* replace slashes with _ in test failure output html files
* re-do out of date PR
* create saved object client that is native javascript
* fix savedObjectClient unit tests
* get saved object client from chrome when being used outside of angular
* update error handlers to pull status code from FetchError
* add some debug messages to failing functional test
* revert changes to management/_objects
* add clicks to import done in import objects test
* take screenshots of test only failing in CI
* remove functional test screenshot code since test is passing in CI now
* remove unused file, clean up saved_objects_client test to not use global, add test to error_auto_create_index to ensure compatibility with kfetch errors
* add body to kfetch error
* update savedObjectClient.bulkCreate
* add bulkCreate wrapper to SavedObjectsClientProvider
* mark _createSavedObject and _processBatchQueue as private methods
The pseudo-element agg-type-select-wrapper::after which represents the dropdown's arrow didn't react to the click element of the dropdown itself. pointer-events: none is now added to the pseudo-elements to let the click pass through to the element intented to react on the click.
- Migrates the ml-info-icon directive to use React/EUI. This fixes a related error in IE11.
- For now a hard-coded override is used to size the icon because EuiIconTip doesn't pass on the size attribute to the wrapped EuiIcon directive.
- The (simple) React component is kept within the directive's, because previously the directive template also wasn't in a separate file.
- Removes the unused mlJsonTooltipService angular service.
Fixes a regression introduced by #19794. This PR added a 5px top margin to the affected charts. The hard coded bottom margin of the progress bars wasn't adjusted accordingly so the progress bars ended up being hidden behind the actual chart. This PR fixes the problem by taking the chart's top margin into account for progressBarMarginBottom.
* Test dependency upon msearch. Add NoDigestPromises to test suite to simplify tests.
* Test the returned promise resolution value.
* Add tests about aborting situations.
* Add test for when the request is aborted while it's in flight.
* Test implementation details regarding interaction with searchRequests.
* Change callClient to return ABORTED for requests which have been aborted.
* Add test verifying that esPromise.abort() is called.
When using yarn link, we are copying the dependencies from the sub-projects. If a new package is
added to one of those projects, we need to also update the yarn.lock file for it's parent. This
is usually done by running `yarn kbn bootstrap`. This ensures that after CI runs bootstrap that
there are no local changes.
