Skip to content

Fix EQL double invoking listener #124918

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

Merged

Conversation

original-brownbear
Copy link
Member

We need to break out early here, otherwise we double resolve the listener in the following code potentially.

More of a suggestion, I don't know enough about this code to write a reproducer but this seemed like the obvious spot for the double resolve.

We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v9.1.0 labels Mar 14, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine
Copy link
Collaborator

Hi @original-brownbear, I've created a changelog YAML for you.

Copy link
Contributor

@luigidellaquila luigidellaquila left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @original-brownbear, LGTM

@luigidellaquila
Copy link
Contributor

This will also need a backport to 8.18, 8.19 and 9.0, I'm adding the appropriate labels

@luigidellaquila luigidellaquila added v9.0.0 v8.18.0 v8.19.0 auto-backport Automatically create backport pull requests when merged labels Mar 17, 2025
@original-brownbear
Copy link
Member Author

Thanks Luigi!

@original-brownbear original-brownbear merged commit c9203e7 into elastic:main Mar 17, 2025
16 of 17 checks passed
@original-brownbear original-brownbear deleted the fix-eql-double-resolve branch March 17, 2025 12:49
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Mar 17, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Mar 17, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this pull request Mar 17, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
9.0
8.18
8.x

elasticsearchmachine pushed a commit that referenced this pull request Mar 17, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
elasticsearchmachine pushed a commit that referenced this pull request Mar 17, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
omricohenn pushed a commit to omricohenn/elasticsearch that referenced this pull request Mar 28, 2025
We need to break out early here, otherwise we double resolve the
listener in the following code potentially.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/EQL EQL querying auto-backport Automatically create backport pull requests when merged >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.18.0 v8.19.0 v9.0.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants