ESQL: Fix IP_PREFIX function leaking data in scratch#141940
Merged
ivancea merged 2 commits intoelastic:mainfrom Feb 5, 2026
Merged
ESQL: Fix IP_PREFIX function leaking data in scratch#141940ivancea merged 2 commits intoelastic:mainfrom
ivancea merged 2 commits intoelastic:mainfrom
Conversation
ivancea
added
>bug
Team:Analytics
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Collaborator
|
Hi @ivancea, I've created a changelog YAML for you. |
MattAlp
approved these changes
Feb 5, 2026
nik9000
approved these changes
Feb 5, 2026
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
ivancea
added a commit
to ivancea/elasticsearch
that referenced
this pull request
Feb 5, 2026
mamazzol
pushed a commit
to mamazzol/elasticsearch
that referenced
this pull request
Feb 6, 2026
This was referenced Feb 9, 2026
elasticsearchmachine
pushed a commit
that referenced
this pull request
Feb 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #141628
There's a case where one byte in the IP_PREFIX scratch isn't cleaned up, and its dirty data gets carried into the generated IP. It's better explained in the linked issue.
Thanks @strawgate for looking into it and identifying the exact bug!