## Summary
* Adds the createEndpointListSchema to the create_endpoint_list_route for API boundary checks
* Adds unit tests to the requests
* Fixes a few bugs found in the find endpoints for types
* Fixes or deletes the skipped tests
* Updated TODO blocks and removed ones that are obsolete
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
Backport #72078 is failing because of the type check because `observer.name` is not defined. Not sure why this wasn't a problem on master, but adding it here so I can include it.
* make hyper parameters one word
* update analytics job types help text
* update job type text
* ensure long description has word break to prevent overflow
* [Maps] fix notifying user about losing unsaved changes when navigating away from map
* clean up
* tslint fixes
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Starting with 7.9.0 we will be dropping support for IE11. Updating the
config to reflect this should minimize the bundle sizes.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* add checkIndexExists endpoint wrapping field_caps
* replace indexNames with checkIndexExists check
* update translations
* show error toast on index check fail
* add new route to api doc
* [ML] Fix job list crashing due to undefined processed records
* [ML] Add explicit undefined check
* [ML] Add check to toLocaleString and update test
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Add a task to gather transasctions telemetry as described in #71593.
Also:
* Fix typo in mapping for country code mapping
* Add back `mergeTelemetryMapping` function to fix broken `upload-telemetry-data` script.
* show empty state when has data returns false
* adding return type
* addressing pr comments
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* rename float to discrete
* use same section title level on all source files
* Elasticsearch => {es}
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This PR removes the validation of `total_by_field_count` for categorization jobs because the number of detected categories is not necessarily stable across analytics changes.
resolves https://github.com/elastic/kibana/issues/70086
Configures the saved object client for the event log to access the recently
hidden action and alert saved objects.
We didn't have tests for action/alert event log activity, so added some now.
Also found a buglet that was preventing access to event log data from actions
and alerts in non-default spaces.
* updates in-app links
* updates links from prebuilt ML jobs
* updates kibana help window text and link
* removes problematic terminolgy from prebuilt job descriptions
* Revert "removes problematic terminolgy from prebuilt job descriptions"
This reverts commit aaa7e2a4ca, as it will be done via the rules repo.
* Revert "updates links from prebuilt ML jobs"
This reverts commit to update links from prebuilt jobs, will be done via the rules repo.
* recommits the link correction after revert
* changes help window app name to Security
* [esArchiver] automatically retry if alias creation fails
* print aliases to a string when logging
Co-authored-by: spalger <spalger@users.noreply.github.com>
* Revert "Skip jest tests that timeout waiting for react"
This reverts commit dd9b0b3274.
* Unmount async effectful components instead of waiting for them
A previous commit introduced waitForUpdates as a solution to the
warnings introduced by https://github.com/enzymejs/enzyme/issues/2073:
by waiting for the effects to complete we avoid the warning.
However, waiting for the effects to complete could occasionally be very
costly, especially on an overtasked CI machine, and I've been seeing
these tests fail on occasion due to timeouts.
Since a warning message is preferable to a false negative, I'm removing
waitForUpdates and allowing the warnings to occur, as this should be
fixed on a subsequent update of enzyme/react-adapter.
I've also fixed warnings in a few particularly problematic/noisy tests
by simply unmounting the component at the end of the test (this does
not work in an afterEach).
