Edited the search session management page font size

[ghost]

Summary

This is a PR for issue #129714

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[Dosant]

@elasticmachine, merge upstream

[Dosant]

buildkite, test this

[Dosant]

@najmiehsa, thank you!

There is a formatting issue https://buildkite.com/elastic/kibana-pull-request/builds/41736#84b58711-81b9-4520-8a04-1a12e0dde488 atm:

ebg [casing] "src/plugins/data/public/search/session/sessions_mgmt/components/table/table.tsx" uses valid casing
--
  | debg [eslint] linting "src/plugins/data/public/search/session/sessions_mgmt/components/table/table.tsx"
  | ERROR
  | /opt/local-ssd/buildkite/builds/kb-c2-8-c5ccee6f799fad80/elastic/kibana-pull-request/kibana/src/plugins/data/public/search/session/sessions_mgmt/components/table/table.tsx
  | 74:18  error  Delete `·`  prettier/prettier
  |  
  | ✖ 1 problem (1 error, 0 warnings)
  | 1 error and 0 warnings potentially fixable with the `--fix` option.
  |  
  | ERROR [eslint] errors

[ghost]

@Dosant Hi, Thank you for the feedback. I know I should run this node scripts/precommit_hook --fix in my local repository.
Once I run the command, I get Error: Cannot find module '@kbn/optimizer' at the moment.
I try to fix this.

[Dosant]

Once I run the command, I get Error: Cannot find module '@kbn/optimizer' at the moment.

have you run yarn kbn bootstrap ? have you been able to start Kibana locally?

This guide should help:
https://www.elastic.co/guide/en/kibana/master/development-getting-started.html

[Dosant]

buildkite, test this

[Dosant]

Actually, in this commit CI automatically fixed prettier: 472607a

[ghost]

Once I run the command, I get Error: Cannot find module '@kbn/optimizer' at the moment.

have you run yarn kbn bootstrap ? have you been able to start Kibana locally?

This guide should help: https://www.elastic.co/guide/en/kibana/master/development-getting-started.html

Thank you.

[Dosant]

I took a look at the fix,

I think we should instead change default size from m -> s here:

kibana/src/plugins/data/public/search/session/sessions_mgmt/components/index.tsx

Line 18 in 0745196

<EuiText size="m" {...props}>

And that should be it

[ghost]

@Dosant I think it is fixed now.

[Dosant]

@Dosant I think it is fixed now.

@najmiehsa, thanks!
I think we don't need changes in src/plugins/data/public/search/session/sessions_mgmt/components/table/table.tsx anymore because this is handled inside a component now.
Could you revert changes in that file, please?

[ghost]

Yes, Sure.

[ghost]

@Dosant I think it is fixed now.

@najmiehsa, thanks! I think we don't need changes in src/plugins/data/public/search/session/sessions_mgmt/components/table/table.tsx anymore because this is handled inside a component now. Could you revert changes in that file, please?

It should be good now.

[Dosant]

@elasticmachine merge upstream

[Dosant]

buildkite, test this

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f71a4aa
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

✅ unchanged

History

• 💔 Build #41774 failed 472607a3533458573ae6fb80194ee9f3d9accd62
• 💔 Build #41736 failed 96129048fbd188fab0d94fb8fa60626fbdafb421

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[Dosant]

@elasticmachine run elasticsearch-ci/docs

[Dosant]

@najmiehsa, Thank you for the contribution 🚀

[ghost]

Thank you.