@Makyen @Undo @ArtOfCode test/test_blacklists.py::test_yaml_nses - whatever test uses websitepixel.co.in in its tests is bad, they've got DNS SERVFAIL meaning their DNS is dead
you'll need to adjust the tests to use a valid domain for testing
we could mock such a domain up if we needed to but
@ThomasWard it worked earlier today and it worked yesterday, I'd say let's wait ... but probably CI should have better DNS caching, and maybe the test should be allowed to fail if the file hasn't changed in the commits we are testing
but the domain was removed from DNS so let's remove it from the blaacklist, too -- the others I had to remove were merely commented out so that we could check back on them, so I can do the same for this one
@ThomasWard this is attempting to verify that we don't add stuff which doesn't work so the test is working exactly as it's supposed to; but we need to be prepared to remove things which should no longer be listed
happened sooner than I anticipated
the test suite already has external dependencies on various things but I agree that basic regression test should probably mock out many of them, and maybe we should have a separate blacklist quality run to alert us about slow regexes and expired domains etc
@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.
[ SmokeDetector | MS ] Pattern-matching website in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (81): Python IDE for Debian by Ethan on softwarerecs.SE
@Machavity That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Pattern-matching website in body, and Pattern-matching website in answer; append -force if you really want to do that.
@Machavity That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
I messed up (again) with feedback on metasmoke.erwaysoftware.com/post/234555. I wanted to report m.erwaysoftware.com/posts/uid/meta/346161, logged into Charcoal HQ, saw a report with what I thought was the same name (ended in Gupta, reported very recently), and TPU'd something which didn't warrant it. Can someone with a MS account please fix it? :/
@tripleee A while ago, I added a couple/few tests which will fail on exceptionally slow blacklist/watchlist regexes. It won't catch everything, but the test cases will fail if there are entries added which are sufficiently slow. The tests are within the !!/bisect command tests. It's currently set such that debugging messages will be displayed by the instance (not in chat) if any of them take more than ~5 times longer than what the high-end of execution time was at the time I picked the levels.
It will cause actual CI failures if the time of one set of 64 regexes is about 50 times what we normally see as a high end, which is about 10 to 15 times less than the amount of time we were seeing on definitely broken regexes. Obviously, how long a regex takes to execute is dependent on the text it's run against. The cases I added were ones which we were already experiencing real-world failures on. The changes were in this PR.
Hey guys, I have a question. I happened to stumble on a chat room (chat.stackexchange.com/rooms/56223/the-spam-blot) on Graphics Design SE, that seems to be some sort of redirection of their Smoke alerts... can this be done for other sites as well?
@DarkCygnus It's possible to have SmokeDetector post spam for selected sites into any specified chat room on a site by site basis. If you want that done for your site(s), we are happy to work with you to set it up.
@DarkCygnus Sure. Into what room would you like them to be reported? Do you want reports for meta-TWP? Do you want posts which are detected only by "experimental" reasons to be reported? "Experimental" reasons are listed here. Notably, those reasons include the watchlist, which will be what detects posts matching regexes we're not sure, yet, if they will have the level of %TP which we wan the blacklist to maintain.
@DarkCygnus Do you want SmokeDetector to accept commands from the room, that would include accepting feedback in the form of chat messages? If so, there are various options as to who is authorized to provide commands/feedback in that room, other than moderators, who are always authorized, if commands are accepted in the room. I described the commonly used configurations for command enabled users within a room in [this message]().
@DarkCygnus Yes, all of these settings can be adjusted later.
@DarkCygnus Also, do you want to mask the title of posts which are identified as having an offensive title (i.e. it's still reported, but the actual title isn't displayed).
@Makyen nice. Ok, for now I think we can go with option B) inherit from here plus room owners, and we can see the engagement we get there to see if we can go for another setting
@DarkCygnus OK. Command/feedback permissions are set per individual, except moderators, who are automatically permitted. Currently, the room only has moderators as room owners, so I'm not adding any specific individuals. I'm happy to add others. To do so is just adding the user to the users.yml file and then to the entry for the room in rooms.yml.
The process of doing that is substantially easier if the user first creates an account on metasmoke, because there's an admin page which provides the information needed for the user formatted as required for those files. However, a metasmoke account isn't required, although it does have some additional benefits for interacting with SD/MS (e.g. adding comments on MS posts, better feedback handling, feedback through the userscripts, etc.).
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +2 more (491): Weight Loss Pills by NathanielMacpherson3 on askubuntu.com
A while back in SOCVR, I asked for close votes on couple question which I came across (while I was searching to see if the question I am answering is an absolute dupe and if I should delete my ans and cast a CV).
Today I was searching for a syntax and found out the same user posted similar questions again and again
