-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Question - Supporting negation cases #49
Comments
Hi @ansrivas - doublestar doesn't support negation, but that could be an interesting feature. For the time being, you could accomplish it by using a very inclusive pattern with |
Thank you for your response @bmatcuk . I also figured we could use that. Seems I should open this as an issue upstream: |
@ansrivas, did you open an issue in upstream about using another Match to exclude results? PS in the mean time, I've created an issue in upstream at grafana/loki#3804 |
Hi @rgl no, unfortunately, we maintained a local fork to work on it. Thanks for opening this upstream. |
@ansrivas Could you publish your local fork? Could you create a PR at grafana/loki? |
Hello! This package is used by the otel-collector, and Im running into an issue where negation is not supported. Is there any workaround or plan to fix? Thanks! |
As part of adikari#20, we want to be able to negate specific paths in a given `watch` path by using `skip_path`. This PR adds support for specifying a `skip_path` option that support either a path or a list of paths that shouldn't result in adding the `trigger` step as part of the dynamically generated pipeline. Note even in cases where a line in the `diff` is skipped due to `skip_path` and there are other paths in the `diff` that match `path` but doesn't match `skip_path`, the step will still be added to the dynamically generated pipeline. i.e. for the step to be effectively ignored, the paths in `skip_path` should match all of those in the given `diff`. This is required due to the lack of support for negation cases in `doublestar`, which we use for glob pattern matching[0]. Closes adikari#20. [0]: bmatcuk/doublestar#49
As part of adikari#20, we want to be able to negate specific paths in a given `watch` path by using `skip_path`. This PR adds support for specifying a `skip_path` option that support either a path or a list of paths that shouldn't result in adding the `trigger` step as part of the dynamically generated pipeline. Note even in cases where a line in the `diff` is skipped due to `skip_path` and there are other paths in the `diff` that match `path` but doesn't match `skip_path`, the step will still be added to the dynamically generated pipeline. i.e. for the step to be effectively ignored, the paths in `skip_path` should match all of those in the given `diff`. This is required due to the lack of support for negation cases in `doublestar`, which we use for glob pattern matching[0]. Closes adikari#20. [0]: bmatcuk/doublestar#49
Hello,
Thank you for your work on this library.
I have a use case where I'd exclude files and include others. I skimmed through the test-cases as well but I couldn't find, hence the query.
Reproducing steps:
Corresponding go-snippet:
Is this by design or it could be a feature worth supporting in the library?
The text was updated successfully, but these errors were encountered: