@Makyen, I’ve been here for a while, and I would like to ask for SD (and MS) privileges. That way, I can use FIRE and AF to their full potential (I’m currently using FIRE in read only mode, and AF without SD), and can report spam and R/A posts I find, as opposed to posting a link and waiting for someone else to report them
@dan1st yeah I was wondering if you should remove it from all the posts since it looks like the user is no more here, might have happened something to them and they did not pay the bills and now someone took it over
@Makyen I need a bigger brain for this; the build failures are not as intermitted as I would hope for, so I suspect a bigger problem, but I can't find it. Sometime after my commit of 0d27da2 but by the time of my next commit of ad552f0, test/test_helpers began failing ...
... to expand https://t.ly/AqjA to https://charcoal-se.org/smokey/, despite my own browser/site expanding it just fine. I don't see any intervening commits at all -- so none that should have changed this behavior. I suspect at this point it's environmental on teward/Cerberus, but that's just a hunch.
well my daughter is sick she has a urinal infection or whatever it's called, but she's not good and doesn't want to take pills with antibiotics, so I'm just afraid she might need to get admitted to the hospital. I'm trying to forget about it, but it's really getting to me. First my stepdad, then me and now her.. life is really something right now
2
Why cant I just have 2-3 weeks without any problems
@JeffSchaller The CI testing is done on compute instances provided by GitHub Actions and Circle CI. They don't run on the active SD instance, so don't have any dependencies on them (i.e., it's not a problem on teward/Cerberus).
@JeffSchaller The problem appears to be that the t.ly either started using CloudFlare, or changed their configuration, such that the response we get back when we give them the honest User Agent of "SmokeDetector/git (+github.com/Charcoal-SE/SmokeDetector)"; doesn't indicate that the URL is forwarded, so trying to get the destination address just results in seeing the source address as the end destination. The response when a User Agent indicating that the requestor is Firefox does indicate that the URL is a forward, and everything works. I've updated SmokeDetector such that we now lie and claim to be Firefox.
@Makyen That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, potentially problematic ns configuration in body (61): How can i recover my lost money from scammers? by Sharon bin on bitcoin.SE
@JeffSchaller In order for a "number" to make an exact match, the pattern must end with a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
@Makyen ahh, yes - I should have remembered my recent GitHub education and known that the CI tests run there. Thank you for getting to the bottom of it! CHQ is a bit less noisy now
