@tripleee That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
STDERR: To github.com:Charcoal-SE/SmokeDetector.git ! [rejected] master -> master (fetch first) error: failed to push some refs to 'git@github.com:Charcoal-SE/SmokeDetector.git' hint: Updates were rejected because the remote contains work that you do hint: not have locally. This is usually caused by another repository pushing hint: to the same ref. You may want to first integrate the remote changes hint: (e.g., 'git pull ...') before pushing again.
### Exception on teward/Solar Flare at 2019-04-24T04:07:57Z: Failed to log into stackexchange.com, max retries exceeded File "ws.py", line 139, in <module> chatcommunicate.init(username, password) File "/home/smokey/SmokeDetector/chatcommunicate.py", line 102, in init raise Exception("Failed to log into " + site + ", max retries exceeded")
### Exception on teward/Solar Flare at 2019-04-24T04:07:50Z: Failed to log into stackexchange.com, max retries exceeded File "ws.py", line 139, in <module> chatcommunicate.init(username, password)
[ SmokeDetector | MS ] Bad keyword in body, link at end of body, link following arrow in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (395): How Does Work Erozon Max? by erozonmax on meta.SE
@double-beep That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@double-beep That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@double-beep That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@double-beep That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
> We are going read-write across the network now that failover has completed. There are a few errors to tidy, but that should be all the user-facing fun for tonight. Thanks for bearing with us!
[ SmokeDetector | MS ] Bad keyword in link text in answer, pattern-matching website in answer, potentially bad keyword in answer (162): Articles in the English ✏️ by Mone1995 on english.SE
[ SmokeDetector | MS ] Bad keyword in link text in answer, pattern-matching website in answer, potentially bad keyword in answer (162): Articles in the English by Mone1995 on english.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more (791): ozvish.com/keto-buzz/ by Aliop Kiop on askubuntu.com
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
