mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
Your window into the Elastic Stack
dc84788112
# Backport This will backport the following commits from `main` to `7.17`: - [ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)](https://github.com/elastic/kibana/pull/220313) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-05-21T04:40:40Z","message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters","number":220313,"url":"https://github.com/elastic/kibana/pull/220313","mergeCommit":{"message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/220313","number":220313,"mergeCommit":{"message":"ScopedHistory Error - Remove calling `verifyAction` assertion from getters (#220313)\n\n## Summary\nThis PR modifies the `CoreScopedHistory` implementation to remove scope\nverification for getter methods while maintaining it for action methods.\nThis change aims to reduce errors occurring during plugin navigation\ntransitions when components are dismounting.\n\n## Background\nCurrently, when components are dismounting during navigation between\nplugins, calls to `ScopedHistory` methods (particularly getters like\n`location`) trigger the\n\n```TypeScript\n`ScopedHistory instance has fell out of navigation scope for basePath: ${this.basePath}`\n```\n\nThis happens because the location's `pathname` has already changed while\nsome components are still in their cleanup phase.\n\n## Changes\n- Removed `verifyActive()` checks from the following getter methods:\n - `location`\n - `action`\n - `length`\n- The following methods still assert `verifyActive()`:\n - `push`\n - `replace`\n - `go`\n - `goBack`\n - `goForward`\n - `block`\n - `listen`\n - `createHref`","sha":"434dd520bdea905efee5dcec6bb7bd68e6883dbe"}}]}] BACKPORT--> Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com> |
||
|---|---|---|
| .buildkite | ||
| .ci | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| licenses | ||
| packages | ||
| plugins | ||
| rfcs | ||
| scripts | ||
| src | ||
| test | ||
| typings | ||
| vars | ||
| x-pack | ||
| .backportrc.json | ||
| .bazelignore | ||
| .bazeliskversion | ||
| .bazelrc | ||
| .bazelrc.common | ||
| .bazelversion | ||
| .browserslistrc | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .fossa.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .i18nrc.json | ||
| .node-version | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| .puppeteerrc | ||
| .stylelintignore | ||
| .stylelintrc | ||
| .telemetryrc.json | ||
| .yarnrc | ||
| api-documenter.json | ||
| BUILD.bazel | ||
| CONTRIBUTING.md | ||
| FAQ.md | ||
| github_checks_reporter.json | ||
| Jenkinsfile | ||
| kibana.d.ts | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| package.json | ||
| preinstall_check.js | ||
| README.md | ||
| STYLEGUIDE.mdx | ||
| tsconfig.base.json | ||
| tsconfig.bazel.json | ||
| tsconfig.browser.json | ||
| tsconfig.browser_bazel.json | ||
| tsconfig.json | ||
| tsconfig.types.json | ||
| TYPESCRIPT.md | ||
| WORKSPACE.bazel | ||
| yarn.lock | ||
Kibana
Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.
- Getting Started
- Documentation
- Version Compatibility with Elasticsearch
- Questions? Problems? Suggestions?
Getting Started
If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.
If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.
Using a Kibana Release
If you want to use a Kibana release in production, give it a test run, or just play around:
- Download the latest version on the Kibana Download Page.
- Learn more about Kibana's features and capabilities on the Kibana Product Page.
- We also offer a hosted version of Kibana on our Cloud Service.
Building and Running Kibana, and/or Contributing Code
You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:
- CONTRIBUTING.md will help you get Kibana up and running.
- If you would like to contribute code, please follow our STYLEGUIDE.mdx.
- For all other questions, check out the FAQ.md and wiki.
Documentation
Visit Elastic.co for the full Kibana documentation.
For information about building the documentation, see the README in elastic/docs.
Version Compatibility with Elasticsearch
Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.
Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.
| Situation | Example Kibana version | Example ES version | Outcome |
|---|---|---|---|
| Versions are the same. | 5.1.2 | 5.1.2 | 💚 OK |
| ES patch number is newer. | 5.1.2 | 5.1.5 | ⚠️ Logged warning |
| ES minor number is newer. | 5.1.2 | 5.5.0 | ⚠️ Logged warning |
| ES major number is newer. | 5.1.2 | 6.0.0 | 🚫 Fatal error |
| ES patch number is older. | 5.1.2 | 5.1.0 | ⚠️ Logged warning |
| ES minor number is older. | 5.1.2 | 5.0.0 | 🚫 Fatal error |
| ES major number is older. | 5.1.2 | 4.0.0 | 🚫 Fatal error |
Questions? Problems? Suggestions?
- If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
- Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.