-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Backport 1.3] Bugfix to guard against stack overflow errors caused by very large reg-ex input #16101
Conversation
…g-ex input (#2810) * Bugfix to guard against stack overflow errors caused by very large reg-ex input This change fixes a code path that did not properly impose the index-level max_regex_length limit. Therefore, it was possibly to provide ar arbitrarily large string as the include/exclude reg-ex value under search aggregations. This exposed the underlying node to crashes from a StackOverflowError, due to how the Lucene RegExp class processes strings using stack frames. Signed-off-by: Kartik Ganesh <[email protected]> * Adding integration tests for large string RegEx Signed-off-by: Kartik Ganesh <[email protected]> * Spotless Signed-off-by: Kartik Ganesh <[email protected]> (cherry picked from commit 566ebfa) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
❌ Gradle check result for fabde0c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Daniel Widdis <[email protected]>
653d12f
to
f86d44e
Compare
❌ Gradle check result for 653d12f: ABORTED Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Daniel Widdis <[email protected]>
❕ Gradle check result for 7eca19d: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Gradle assemble is failing, do we need to backport something else to this branch @dbwiddis ? |
It's only failing on macOS. Apparently we don't have docker there (at least on 1.3?) Interestingly, it showed able to merge before I added the changelog commit. |
Ah, I see, the GHA doesn't like the changed name to macos-13:
EDIT: oops. that was matrix.os. runner.os is apparently |
Well, that didn't fix it. The action on |
d6a157c
to
7eca19d
Compare
Backport 566ebfa from #2810.
This was backported to 1.x in #8663 but never made it to 1.3. Encountered in the wild today, 58 nodes dropped at once, whee!