-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Delay client-side feature usage registration until start #79365
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
Conversation
|
Pinging @elastic/kibana-platform (Team:Platform) |
legrego
left a comment
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, tested locally and this resolves the issue I was seeing on the login selector screen. Thanks for the fix!
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]page load bundle size
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…) (#79857) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
… (#79856) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
This fixes works around a race condition in the AnonymousPaths service where not all anonymous paths may be registered until setup completes. Plugin execution order changes can result in exposing this race condition. To fix this entirely, we should remove the
core.http.anonymousPaths.isAnonymousAPI from CoreSetup, but that will be a much larger change.Checklist
For maintainers