Skip to content
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

[React@18 QA] @elastic/security-team-threat-hunting-explore #212190

Closed
4 tasks done
kapral18 opened this issue Feb 23, 2025 · 4 comments
Closed
4 tasks done

[React@18 QA] @elastic/security-team-threat-hunting-explore #212190

kapral18 opened this issue Feb 23, 2025 · 4 comments
Assignees
Labels
Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Explore Team:Threat Hunting Security Solution Threat Hunting Team
Milestone

Comments

@kapral18
Copy link
Contributor

kapral18 commented Feb 23, 2025

Description

Kibana needs to be upgraded to use React 18. This should be done prior to 8.last so we do not have a long support period for a Kibana version using an unsupported version of React.

Each team needs to test the part of the UI they own to make sure that nothing is broken.

Original issue: https://github.com/elastic/kibana-team/issues/1016
Parent issue: #203114

How to test

Testing can be done locally by using the PR (#209337) or from main with REACT_18=true ENV flag:

REACT_18=true yarn bootstrap
REACT_18=true yarn start

You can also use cloud or serverless deployment from that #209337.

Tip

  • Locally you can tell that you're running React@18 by the following message in the console: Kibana is built with and running [email protected], muting legacy root warning.
  • When deployed and when having React Dev Tools extension you can check the version with __REACT_DEVTOOLS_GLOBAL_HOOK__.renderers.get(1).version in console

What to look for

Tip

Look for blank screens, error splash screens, unresponsive pages, new errors in the console, unpredictable UI behavior (like laggy text inputs that skip letters when typing fast). You can also review the list of addressed runtime issues discovered by functional tests in the section below

Features

  • data quality dashboard
  • explore users
  • explore network
  • explore hosts
@kapral18 kapral18 self-assigned this Feb 23, 2025
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 23, 2025
@kapral18 kapral18 added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. and removed needs-team Issues missing a team label labels Feb 23, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@kapral18 kapral18 added Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Explore labels Feb 23, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)

@kapral18
Copy link
Contributor Author

Testing is successful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Explore Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

No branches or pull requests

2 participants