Numpy and Python are getting into a turf war of what the double equals and 'in' operator should do when the left hand side is a primitive string and the right hand side is a numpy ndarray. Naturally the numpy people want it to return an ndarray of boolean, but that's not Pythonic, python people say it should return a Scalar of True/False if the element is in the array. What should happen when the left type and right type is of disparate types, like string and numeric ndarray? Who knows.
It's like the Tabs vs Spaces world. Numpy is trying to encroach to take over what Python considers Python. Many codes will be broken before the tabs vs spaces argument is finished.
@Andy Pandas, Matplotlib, and many others python libraries are affected by this FutureWarning. The way to protect yourself from it is whenever you're comparing a python primitive type to a numpy ndarray type, you're asking for trouble. Neither the 'in' or '==' operators are safe.
Numpy Reign of terror is now. They're trying to take over your in and == operators and make them into Numpy's bizarre array slicing philosophy.
but in their defense, the user did import numpy. But that doesn't give them license to change the contracts of double equals and in operators. Ugh, endless debate.
@Andy Messages from SmokeDetector in Charcoal HQ are generally kept as records. If you really need to delete a message, please use sd delete-force. See this note on message deletion for more details.
@Andy Oh yeah lol, I hadn't thought of that. You import some library that uses pandas, and you pass it some innocent primitive type, and it pukes on the carpet because numpy ndarray array slicing behavior under the hood are changing.
It was a fork I made with the aim of rewriting SmokeDetector from the ground up as part of a port to Python 3. It pretty much works but I didn't get enough momentum to port all of SmokeDetector's spam checks to it
I came back to it to see if it would be easier to port any of the several new systems back
chat seemed the most useful and easiest relatively
which is saying a lot because I've changed thousands of lines
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +3 more: alphajackedhelp.com/androdrox/ by Matther on askubuntu.com
tpu- by Tetsuya Yamamoto
CI on 5cb70fa succeeded. Message contains 'autopull', pulling...
@tripleee That pattern looks like it's already caught by Bad keyword in answer, Pattern-matching website in answer, Bad keyword in body, and Pattern-matching website in body; use !!/blacklist-website-force if you really want to do that.
@tripleee Added beautysecretanswers\.com to watchlist
[ SmokeDetector | MS ] Blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title, +1 more: Plus Iq Points-Review by serjohn on meta.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: It starts to take them a touch longer by cadaw on graphicdesign.SE
[ SmokeDetector | MS ] URL in title, bad NS for domain in title, bad keyword in body, bad keyword in title, blacklisted website in title: bellasvish.com/androdrox/ by usaeuca on graphicdesign.SE
CI on cc9121a succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at [rev cc9121a (SmokeDetector: Auto blacklist of test[ -]reload by tripleee --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/cc9121a) (running on Henders/EC2)
Restart: API quota is 9635.
CI on fb5506d succeeded. Message contains 'autopull', pulling...
[ SmokeDetector | MS ] 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: facts4fitness.com/androdrox/ by cham prana on apple.SE
