[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: www.7supplements.org/lumanere/ by gaonwoidbn24 on workplace.stackexchange.com
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, repeated URL at end of long post: wellnessfeeds.com/lumanere/ by DottiGarr on graphicdesign.stackexchange.com
tpu- by Glorfindel
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: risingsupplements.com/alpha-x-boost/ by pecri nuclu on apple.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Lumanere Skin Solution by tonon nosi on drupal.stackexchange.com
This is for the most part completed:
Two rollbacks from the same user on a single post will generate a "rollback war" auto-flag for moderator attention.
An edit which causes a post to become "low quality" will bump the post into the Low Quality Posts review queue if the edit is live for more th...
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: The Natural Way To Less Wrinkles by Txszsloi on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, repeated URL at end of long post, blacklisted user: Lumanere Serum Beauty face by pecri nuclu12 on apple.stackexchange.com
@SmokeDetector hmm, I gave them the benefit of the doubt
he was disclosing his affiliation and didn't seem to be particularly promoting his workplace, just including it, presumably out of lack of familiarity with SO
but I'm not entirely comfortable with how things are currently defined; for example, to be able to properly categorize, I think we'd need NAQ in parallel to NAA for questions which are just ... not
@ArtOfCode @Undo I'd like to be able to put in a try/except catch on that section that used to have the infinite loop, at least as a temporary "debugging" commit, before I attach the debugger - that way I can set the breakpoint before the exception handler gets called, which will in turn give me a better snapshot than when it errors out. The fact we have the exception handler is why i need to put a temporary workaround to 'freeze' before that is called. If there's no objection.
(would be as simple as something like except: and raise RuntimeError("This should not trigger, if it does the debugger is broken.") with a breakpoint on the raise)
then when I load Smokey in a debugger later this afternoon we can track the invalid literal error better
i'll add it later, thanks @ArtOfCode. The error will still get caught, of course, but with a slightly different error message.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Lumanere Serum eyelids by pecri nuclu on superuser.com