@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.
CI on a73535d succeeded. Message contains 'autopull', pulling...
@tripleee 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.
That's true. OTOH it contains the name company and the link is in the user's profile. (At the very least, it is blatantly off-topic, but I went for spam flag.)
@tripleee 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.
WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. 2018-08-22 05:04:50.899780 UTC
WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. 2018-08-22 05:05:20.926695 UTC
WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets. 2018-08-22 05:05:51.143900 UTC
WARNING: Last metasmoke ping with a response was over 120 seconds ago, forcing SmokeDetector restart to reset all sockets.
File "/usr/local/lib/python3.6/dist-packages/websocket/_core.py", line 211, in connect options.pop('socket', None))
File "/usr/local/lib/python3.6/dist-packages/websocket/_http.py", line 64, in connect hostname, port, is_secure, proxy)
File "/usr/local/lib/python3.6/dist-packages/websocket/_http.py", line 93, in _get_addrinfo_list hostname, port, 0, 0, socket.SOL_TCP)
File "/usr/lib/python3.6/socket.py", line 745, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
@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.
@tripleee That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer; append -force if you really want to do that.
@tripleee Git functions failed for unspecified reasons, details may be in error log.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, +1 more: Phenterage Garcinia Australia by courtnailey on graphicdesign.SE
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, potentially bad ns for domain in body: Live Flings Dating by ZuriePetrie on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, potentially bad ns for domain in body: Max Forte Booster Canada by gallinasro on superuser.com
tpu- by Shree
CI on ce37775 succeeded. Message contains 'autopull', pulling...
@Shree 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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body, +2 more: Keto Fire Diet The fourth advantage by courtko on graphicdesign.SE
@tripleee That pattern looks like it's already caught by Bad keyword in answer, Mostly non-latin body, Mostly non-latin answer, and Bad keyword in body; append -force if you really want to do that.
@tripleee I just got to work from my commute, I'll take a look soon to see if Solar's the one complaining. It sounds like what happened is that we had two people blacklist or watchlist simultaneously
they come up surreptitiously from time to time, that didn't use to happen before so it's really not feasibly to do !!/location before each !!/watch (and even if you did there is a race condition)
@Undo @ArtOfCode how hard would it be to add a function to MS that reports which Smokeys are in 'active' mode?
because we apparently now need to test if more than one instance is active, and not do Git functions if there's more than one - it'd rule out the headaches that Solar is having right now caused by two instances running and handling the same blacklist request (it broke the tree massively so now I have to fresh clone Solar Flare)
because this would be a Smokey/gitmanager check to prohibit two systems from handling the same task at the same time for git commands such as blacklisting or watchlisting
@ArtOfCode Solar Flare's merge problem was that it and another instance were both handling the same blacklist/watchlist call at the same time
and a race happened
it broke Solar Flare's tree enough that I had to reclone it
but if we had a check to see if there's two Smokeys online when a !!/blacklist or such command is called we can counter the race condition with a check against MS for the data. And if MS is down we just assume there isn't more than one
hence where the inquiry as to whether the feature for a machine-readable version of status existed
