@JeffSchaller That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 906-570-6696 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 906-570-6696. Append -force to the command word(s) if you really want to add the pattern you provided.
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if there are any operational notifications from Thomas Ward, which are usually pinned in the sidebar. If Thoth is operational (i.e. use the !!/location command to see if it responds), then consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. @Makyen
### LoginError on teward/Cerberus at 2024-11-24T02:15:17Z: login with cookie could not be verified, try credential login instead File "/home/smokey/SmokeDetector/chatcommunicate.py", line 120, in init client.login_with_cookie(cookies[site]) File "/home/smokey/SmokeDetector/venv/lib/python3.12/site-packages/chatexchange/client.py", line 180, in login_with_cookie self._br.login_site_with_cookie(self.host, cookie_jar) File "/home/smokey/SmokeDetector/venv/lib/python3.12/site-packages/chatexchange/browser.py", line 176, in login_site_with_cookie
@JeffSchaller Sorry, I thought you were aware, yes, that's my assumption too. It's happened multiple times over the last couple/few days. However, it only started happening since @ThomasWard updated the underlying system, so it's possible that had some impact. But, I'm betting on Cloudflare.
@Dragonrage For performance reasons, please use non-capturing groups, (?:), rather than capturing groups, (), unless your regex requires using a capture group for functional reasons. If your regex requires a capture group, then you will need to use a named capture group, rather than an unnamed group, due to not knowing what other capture groups are being used in the full regular expression that is made up of all the entries on the blacklist or watchlist.
sdc report stackoverflow.com/a/79219295 "ChatGPT with a link to the user's website. I've custom flagged it but posting it here to register the website"
@Cow That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Cow That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 854-410-5314 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/watch-number 854-410-5314. Append -force to the command word(s) if you really want to add the pattern you provided.
@Fastnlight That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 809-913-0508 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 809-913-0508. Append -force to the command word(s) if you really want to add the pattern you provided.
@SmokeDetector Hmmm... That's not the commit that should have been pulled, as it hasn't passed CI, yet. So, we have a timing issue wrt. when MS sends a WebSocket message saying the CI testing is complete and SD pulling. I expect we need to have a check for the current HEAD having actually passed CI testing, as we do for the !!/pull command.
I've looked up the user's history before to determine if a username blacklist would be okay. That post gave me pause since it was FP, and I wasn't sure if we should make an exception since all of their subsequent posts have been trolling. At the time, I decided against changing my feedback since the post was, on the surface level, not an obvious troll and because I could not find any clear affiliation between them and the linked blog post.
