Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
# Backport This will backport the following commits from `main` to `8.x`: - [Add refresh for event log, when we fill gap (#209906)](#209906) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Khristinin Nikita","email":"nikita.khristinin@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T11:31:49Z","message":"Add refresh for event log, when we fill gap (#209906)\n\n## Add refresh for event log, when we fill gap \r\n\r\nAs we update gaps, and don't wait for refresh in UI we can have\r\ninconsistent state:\r\n\r\n- Go to gap table\r\n- Click fill gap, wait for api response\r\n- Then we refetch gaps, but because we don't wait for refresh we get old\r\ngaps and action \"Fill gap\" still remain in the table\r\n\r\nIn this PR we introduce index refresh, which only happens when user make\r\nan action to fill gap\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fd7c7591daacf68fcc628515687ed1f1f839c589","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v9.1.0","backport:8.18"],"title":"Add refresh for event log, when we fill gap","number":209906,"url":"https://github.com/elastic/kibana/pull/209906","mergeCommit":{"message":"Add refresh for event log, when we fill gap (#209906)\n\n## Add refresh for event log, when we fill gap \r\n\r\nAs we update gaps, and don't wait for refresh in UI we can have\r\ninconsistent state:\r\n\r\n- Go to gap table\r\n- Click fill gap, wait for api response\r\n- Then we refetch gaps, but because we don't wait for refresh we get old\r\ngaps and action \"Fill gap\" still remain in the table\r\n\r\nIn this PR we introduce index refresh, which only happens when user make\r\nan action to fill gap\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fd7c7591daacf68fcc628515687ed1f1f839c589"}},"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/209906","number":209906,"mergeCommit":{"message":"Add refresh for event log, when we fill gap (#209906)\n\n## Add refresh for event log, when we fill gap \r\n\r\nAs we update gaps, and don't wait for refresh in UI we can have\r\ninconsistent state:\r\n\r\n- Go to gap table\r\n- Click fill gap, wait for api response\r\n- Then we refetch gaps, but because we don't wait for refresh we get old\r\ngaps and action \"Fill gap\" still remain in the table\r\n\r\nIn this PR we introduce index refresh, which only happens when user make\r\nan action to fill gap\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"fd7c7591daacf68fcc628515687ed1f1f839c589"}},{"url":"https://github.com/elastic/kibana/pull/210338","number":210338,"branch":"9.0","state":"OPEN"}]}] BACKPORT-->
- Loading branch information