raise ConfigError when same label appears twice, or no match appears in label #1233
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.
This change fixes the 2
<label>
related bugs:no
<match>
sections in<label>
isn't reportedThis is clearly wrong configuration, and warning "no patterns matched" appears always for
@test
label.This change raises configuration error for such configuration.
same label configured twice
Currently, Fluentd uses the last configuration for same labels without any errors nor warnings.
This configuration is clearly a misconfiguration. So this change is to make to report such configurations as errors.