@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen Ha... Fixed it by undeleting the branch before the CI tasks needed it. :-) Either that, or I'd waited just barely long enough prior to !!/approve.
@Makyen 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.
@Makyen 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.
@Makyen 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.
@Makyen 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.
@Makyen 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.
@Makyen 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.
@Makyen Sometimes it comes back and reads the intervening commands.
Basically, Sandy Shores has intermittent issues with forking processes, or at least that's what it looks like. It appears to be similar to a system level lack of resources issue (e.g. running without enough virtual memory defined).
@Makyen 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.
probably needs more testing still; in particular I'm guessing the keys will need to be sorted alphabetically in order for this to make sense going forward
("sense" as in "you can reasonably predict the order of the keys when searching")
BTW: If you're interested, the script run_tests.sh in the SD repository can be used to run the tests on linux platforms from your local files. However, it assumes that requirements.txt and user_requirements.txt have already been installed via sudo pip3 install -r requirements.txt --upgrade and pip3 install --user -r user_requirements.txt --upgrade. It's also possible to use it to run the tests on Windows.
Alternately/in addition, it's possible/easy/free to set up Circle CI to automatically run on your GitHub fork, the same as it does in Charcoal-SE/SmokeDetector. However, if you do, you have to be sure to push your branch to Charcoal-SE/SmokeDetector and make the PR from the branch in Charcoal-SE/SmokeDetector, or the results of the CI testing won't be shown in the PR.
@Makyen 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.
Right now the spam tag is labeled as
Exsits only to promote a product or service, does not disclose the author's affiliation.
and in the author's affiliation it says
"The community here tends to vote down overt self-promotion and flag it as spam..." and "Don't talk about your product...
@Makyen Should I check that room for confirmation in the future? I knew it was meant to be for debug-type responses, but I've seen them still posted here.
@Das_Geek They should be posted in both rooms. However, given how SD is written, it's possible that the chat rate limiting will prevent posting beyond the point when SD actually reboots, at which point if forgets that it should have posted something. SD posts significantly fewer messages into the chat.SO domain. Thus, it's much more likely that messages will show up there. Chat rate limiting was the primary reason for creating that room on chat.SO. This is just one of the possible effects.
To be clear: chat rate limiting is per Stack Exchange chat domain. Thus, posting on chat.SO has no effect wrt. rate limiting on chat.SE or chat.MSE.
@SmokeDetector This is either someone just trolling, or is an NAA from someone well under the age which is required for using the site. I've custom mod-flagged.
@Makyen Cool, appreciate the explanation. Is the error Smokey is throwing specifically to do with the PR process? It seems to only happen on my watch-es :P
Right now the spam tag is labeled as
Exsits only to promote a product or service, does not disclose the author's affiliation.
and in the author's affiliation it says
"The community here tends to vote down overt self-promotion and flag it as spam..." and "Don't talk about your product...