-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix some unhandledRejections #168009
Fix some unhandledRejections #168009
Conversation
65081c9
to
1195c19
Compare
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @afharo |
Pinging @elastic/kibana-security (Team:Security) |
Pinging @elastic/ml-ui (:ml) |
Pinging @elastic/kibana-presentation (Team:Presentation) |
Pinging @elastic/uptime (Team:uptime) |
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/appex-sharedux (Team:SharedUX) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
response ops changes lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ML/AIOps related changes LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
presentation changes lgtm! thanks for resolving this! 😄
code review and tested links embeddable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
(cherry picked from commit baff0eb)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.11`: - [Fix some unhandledRejections (#168009)](#168009) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2023-10-06T11:44:52Z","message":"Fix some unhandledRejections (#168009)","sha":"baff0eb32c894eed537bb563068c9743e98e2412","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","performance","Team:Security",":ml","Team:Presentation","Team:uptime","release_note:skip","Team:ResponseOps","Team:ML","Team:SharedUX","backport:prev-minor","Team:Performance","v8.12.0"],"number":168009,"url":"https://github.com/elastic/kibana/pull/168009","mergeCommit":{"message":"Fix some unhandledRejections (#168009)","sha":"baff0eb32c894eed537bb563068c9743e98e2412"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/168009","number":168009,"mergeCommit":{"message":"Fix some unhandledRejections (#168009)","sha":"baff0eb32c894eed537bb563068c9743e98e2412"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
Summary
While stress-testing Kibana, I noticed that it triggered a few unhandled rejections.
Some of them were caused because we provided an async method to
RxJS.Observable.subscribe
. Subscribe can only run synchronous methods. If any async operations are needed, they should be done via(switch|concat|merge)Map
. There are a bunch of other usages, but all of them are in thepublic
codebase. While we'll need to spend time fixing those, a failure there wouldn't crash the server.I also noticed that UI Settings read method might throw an unhandled rejection. But I was not able to find the caller that calls it without handling the rejection. cc @elastic/kibana-core, we should look further into that.
For maintainers