Open
Conversation
|
I wonder if a simple flag to suppress these messages could be a better solution. |
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
2 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.
We see certain hosts submitting invalid data into alfred.
This data makes alfred-json emit a warning twhich in turn triggers cron emails.
The PR adds a simple blacklist functionality to ignore those hosts. This way do not have to suppress all all output from cron json and therefore still receive notifications about other problems.
The patch could use some cleanup which I will perform if I get a general positive feedback.
cc: @christf @oszilloskop @MyIgel