[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: Booty Pop Review? by ericadstern on askubuntu.com
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; use !!/watch-force if you really want to do that.
@tripleee Added (?<=/)blue\W?pearl(?:[-/<]|$) to watchlist
tpu- by Tetsuya Yamamoto
CI on c0dc0d6 succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at [rev c0dc0d6 (SmokeDetector: Auto watch of (?<=/)blue\W?pearl(?:[-/<]|$) by tripleee --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/c0dc0d6) (running on Henders/EC2)
@tripleee you know if you could make the output more compact (ideally one message per report with the relevant parts) I think it would be good if half life ran in here even if it's still WIP
@quartata we discussed having it produce JSON instead of just a set of free-form log entries, I think Ashish might have started on that but it's been a few weeks
then Pulse (or whichever other client) could format the output into something suitable for another channel or purpose
I have a bunch of trivial fixes for the analysis logic queued up in my mind, maybe I can do the JSON change as well once I find the time
@quartata because the watch gets executed in a context where it needs to be adjacent to a word boundary ... so if you make a leading slash (or plus, period, etc) part of the regex, it won't match in a context like foo/blue-pearl
foo//blue-pearl would match IIRC, foo/ gets accepted as context and then /blue-pearl matches (but I haven't checked, this could be wrong but nevertheless illustrative)
@tripleee That pattern looks like it's already caught by Mostly non-latin answer and Mostly non-latin body; use !!/watch-force if you really want to do that.
@tripleee That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; use !!/blacklist-website-force if you really want to do that.
@tripleee That pattern looks like it's already caught by Mostly non-latin answer and Mostly non-latin body; use !!/blacklist-keyword-force if you really want to do that.
