@Machavity 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.
@ThomasWard Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for openbenchmarking.org are in set {'162.252.83.89'}
@JeffSchaller Given that the only reason indicated in the report is the watch you added, it looks like SD would have originally scanned it and not reported it.
As to how well SD keeps up, SD has a queue for each site. Sites have to have X new things to scan prior to SD making an SE API call to get the posts. For the vast majority of sites, X is 1. On larger sites, X is higher in order for SD not to run out of SE API quota. Usually, SD will scan things within seconds of when they are posted/edited, but it can be minutes. In rare cases, it can be longer.
Prior to changing the queue depth for most sites to 1, there were many times where it would be quite a while prior to SD scanning a post. At this point, the problem we encounter more often is SD scanning the post and then users editing during the grace period to add spam. Unfortunately, SE has no way to be notified of grace period edits, so SD detecting users adding spam/R/A content in a grace period edit is an issue that hasn't been resolved yet.
@double-beep Did you try to re-follow the project?
@double-beep There will probably be something that you need to do on the linked page. It's also possible that something resulted in your OAuth for CircleCI being revoked in your account, but I would have expected a different message if that is what happened. I'm not seeing anything in the project that should have resulted in CircleCI thinking you no longer had access.
It's possible the GitHub API started reporting "Triage" access differently and CircleCI hasn't adapted.
@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.
... this might sound strange but I'd rather not have a Stack Overflow account linked to this current account, for now at least. Hence the above creation
(can't invalidate my feedback without an account it seems?)
@Makyen hmmm... it appears that the OAth for CircleCI was revoked, but not sure how. I have reconnected CircleCI to GH and followed Charcoal/SmokeDetector
@Jenayah I'm not sure why your prior feedback was not automatically overwritten. MS thinks that they came from the same chat user ID, so I would have expected the older one, which was given within the last 24 hours, to have been overwritten. I guess it might require an associated MS account in order for the overwrite to happen, but I haven't looked at the code for it. I've cleared the original tpu, as that appeared to be what you wanted.
@double-beep Sounds good. I don't know why the OAuth would have been revoked. That's wrt. your GitHub account, so you're the only one that wil be able to get more info on that.
