Cherry-pick #21282 to 7.x: stop monitoring excluded paths #22486
Conversation
This file contains 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
botelastic
bot
added
the
needs_team
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
removed
the
needs_team
❕ Flaky test reportNo test was executed to be analysed. |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
marc-gr
force-pushed
the
backport_21282_7.x
branch
2 times, most recently
from
7f1a32b to
be8fcac
Compare
marc-gr
force-pushed
the
backport_21282_7.x
branch
from
be8fcac to
b4480b9
Compare
If the files match the excluded pattern, recursiveWatcher does not emit events for them, as well as errors if any. (cherry picked from commit af8eedd)
marc-gr
force-pushed
the
backport_21282_7.x
branch
from
b4480b9 to
1ebdc56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-pick of PR #21282 to 7.x branch. Original message:
What does this PR do?
If the files match the excluded pattern,
recursiveWatcherdoes not emit events for them, as well as errors if any.Why is it important?
This eliminates unnecessary warning logs for file paths that user intends to exclude.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
run test case
TestRecursiveExcludedPathsRelated issues