## Summary
Changes the error handling for when responses are returning with errors from the backend. We were aggregating on error status codes, but this will aggregate on the error reason per rule run and report those instead.
* Adds a utility function
* Adds unit tests for the utility function
* Adds TypeScript Types for the utility function
* Adds sample helpers for the mocks for testing
### Checklist
- [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
* Routes dependencies updated (except for routes itself)
* Replace all chrome deps except map controller
* Replace npSetup and npStart with normal plugin init logic. Some clean up
* Bind kibana services in map controller
* Use kibana services in map controller
* Convert remaining deps that aren't critical to legacy operation
* Remove last angular bindings to gis map saved object loader
* Consolidate kibana services in NP
* Some fixes. Remove console logs
* Fix type errors
* Fix jest test path refs
* Accomodate legacy 'hacks' and init services for vis type alias
* Review feedback. Remove/update unused declarations
* getFileUpload actually just needed Component tacked on the end
* Handle visibility of toolbars for full screen mode using new core chrome. Should fix test
* Import source types in getInitialLayers to ensure registry
* move away from joi
* update schema for filterQuery
* fix types
* update schemas
* remove boom
* remove redundant params
* reuse utils from case
* update schemas for query params and body
* fix types
* update validation schema
* fix unit test
* update description for test cases
* remove import from case
* lifting common libs
* fix dependency
* lifting validation builder function
* add unit test
* fix for code review
* reve comments
* rename common utils
* fix types
Work on #61313 has revealed that we don't have amock for AlertServices, which creates coupling between us and any solution depending on us, which makes it harder to make changes in our own code.
This PR adds mocks and uses them in SIEM, Monitoring and Uptime, so that we can make future changes without having to change outside solutions.
* [Reporting] Add "warning" as a status
* test
* fix warning status handling
* Simplify logic
* fix syntax
* more different statuses
* fix warning
* feedbacks
* [Lens] Only show copy on save for previously saved docs
* Update app.test.tsx
import after kibana platform changes
Co-authored-by: Marta Bondyra <marta.bondyra@gmail.com>
## Summary
Changes some types around so modifying redux state or actions will cause type errors
* the state and action types aren't using `Immutable` directly. This means that you can instantiate them and mutate them
* the `state` and `action` params received by all reducers will be automatically cast to `Immutable`
* reducers can return either `Immutable` or regular versions of `state`
* some code may be mutating redux state directly, this is being ignored (at least for now)
* Use of testSubjects.setValue
* Add waitForEditAlertFlyout
* Fix some extra flakiness
* Test half second sleep to confirm cause of flakiness
* Revert 02417961f9
* Try clearWithKeyboard
* Fix test failures
* Fix uptime tests
* Revert uptime changes
* Add embeddable via saved object example
* give todoRefEmbed a different name from the by value one
* fix types
* fix order of unmounting
Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
* x-pack/watcher: use Elasticsearch from CoreStart
* x-pack/upgrade_assistant: use Elasticsearch from CoreStart
* x-pack/actions: use Elasticsearch from CoreStart
* x-pack/alerting: use Elasticsearch from CoreStart
* x-pack/lens: use Elasticsearch from CoreStart
* expressions: use Elasticsearch from CoreStart
* x-pack/remote_clusters: remove unused Elasticsearch dependency on CoreSetup
* x-pack/oss_telemetry: use Elasticsearch from CoreStart
* Cleanup after #59886
* x-pack/watcher: create custom client only once
* Revert "x-pack/watcher: create custom client only once"
This reverts commit 78fc4d2e93.
* Revert "x-pack/watcher: use Elasticsearch from CoreStart"
This reverts commit b621af9388.
* x-pack/task_manager: use Elasticsearch from CoreStart
* x-pack/event_log: use Elasticsearch from CoreStart
* x-pack/alerting: use Elasticsearch from CoreStart
* x-pack/apm: use Elasticsearch from CoreStart
* x-pack/actions: use Elasticsearch from CoreStart
* PR Feedback
* APM review nits
* Remove unused variable
* Remove unused variable
* x-pack/apm: better typesafety
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Move TSVB into new platform
* Get rid of isFunction checks
* Remove extra import of styling constants
* Move styles importing into plugin.ts
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
getHref on Action interfaces in uiActions plugin is now async. getHref is now used only to support right click behaviour. execute() takes control on regular click.
This add completion support for the csv, circle, geoip, html strip,
inference, set security user, urldecode and user agent processors to the
dev tools console.
Detects if a task run failed due to the task SO being deleted mid flight and if so writes debug logs instead of warnings.
Detects if an Alerting task run failed due to the alert SO being deleted mid flight of the task and if so ensures the task doesn't reschedule itself (as it usually would with other types of tasks).
Ensures that the operation of deleting or disabling an Alert won't fail if it fails to delete an already deleted task (a task might preemptively self delete if its underlying alert object was deleted, even if the overall delete operation wasn't deleted).