[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, body starts with title and ends in URL, link at end of body, +1 more: Gleam And Glow Cream by user840549 on askubuntu.com
@Mithrandir That pattern looks like it's already caught by Pattern-matching website in body, Pattern-matching website in answer, Bad ns for domain in answer, and Bad ns for domain in body; append -force if you really want to do that.
@Mithrandir the threshold is still officially 3/3 though I have been thinking along similar lines, 2/2 for a new Indian pharma domain or product over the last few days?
for one of the previous upgrade operations I created a Github ticket but I guess it wasn't clear enough ... I was thinking we would close the ticket only when we have verified each instance
Smokey runners: One of our dependency has updated. Please pull and run install_dependencies.sh again on your server. Check the box for your instance on this thread after you've done so we can decide when to remove compatibility with the old version.
Metasmoke has a bunch of migration scripts, maybe we should have something similar in SmokeDetector for "I don't know what I need to do but I should probably update"
there's another problem: we need to find a way to ensure a startup hook is run only once. You don't want pip to take a lot of time just to check if the pkgs are up-to-date every time, right?
> pytest 3.6.1 has requirement py>=1.5.0, but you'll have py 1.4.34 which is incompatible. chatexchange 0.0.3 has requirement coverage==3.7.1, but you'll have coverage 4.5.1 which is incompatible.
I've been out of the Smokey game for the last few months and I have an important matter to attend to later today, so I won't be able to test and validate my setup until later.
I added checkboxes to the ticket and reopened it, can you please review? There are many instances which haven't been active for months so I didn't include those
obtaining an AWS instance and setting up a new Smoke Detector instance there should not be a serious undertaking, especially if you are in the free tier for AWS
[ SmokeDetector | MS ] Few unique characters in answer, luncheon meat detected, no whitespace in answer, repeating characters in answer: Python Phonebook by lol on stackoverflow.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-13: elfsight.com Body - Position 1-13: elfsight.com Username - Position 1-13: elfsight.com
@doppelgreener 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.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-11: testorigen Body - Position 1-11: testorigen Username - Position 1-11: testorigen
@tripleee Happy to see what you come up with. The problem I forsee is it will be the same as the previous phone number detection that was already attempted (and then later disabled) - it'll catch an insane number of false-positives and not be a useful rule.
the key though is the CPUs - the CPUs aren't shared they're dedicated to that system, so I can peg the CPU all I want for computation and compiling and such without issue
think of them this way, Docker is an application-level container, running only the specific application and its dependencies per the configurations provided.
LXD is a full OS container which you can run things inside of as if it's its own system.
you can run a full OS container in Docker, but it wasn't written to do that.
[ SmokeDetector ] SmokeDetector started in standby mode at [rev fc94f61 (SmokeDetector: Auto watch of [a-z_]*(?:234_)?812[\W_]*364[\W_]*5598[a-z_]* by tripleee --autopull*)](//github.com/Charcoal-SE/SmokeDetector/commit/fc94f61) (running on ArtOfCode/EC22)
room topic changed to Charcoal HQ: Where diamonds are made, smoke is detected, and we break things by developing on production. 98k true positives and counting. Handy links: charcoal-se.org, github.com/Charcoal-SE, charcoal-se.org/blaze, metasmoke.erwaysoftware.com [best-bad-practices] [corn-for-horse] [crazed-maniacs] [dev-on-prod] [everything-is-broken] [failure-as-a-service] [panic-driven-development] [plastic-knives] [programmatic-crowbars] [roadkill-pasta]
