-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[RAM] Correct renamed function after a race-condition merge #167026
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
💔 Build FailedFailed CI StepsTest Failures
Metrics [docs]
HistoryTo update your PR or re-run it, just comment with: |
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!
Merged despite a flaky test, this should not be related to this fix. |
…167026) ## Summary There was an accidental race-condition on a variable re-name and usage between elastic#166032 & elastic#166603. This PR intends to correct that. (cherry picked from commit e2a7157)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Summary
There was an accidental race-condition on a variable re-name and usage between #166032 & #166603.
This PR intends to correct that.