@ArtOfCode i wonder if the CPU credits thing was causing those socket problems with the SSL stuff, that it just ran out of credits and halted briefly and it caused problems?
@ArtOfCode I know I prodded Undo, but the git process that automatically copies commits from master to deploy stopped, I think due to the GH outage from earlier
can you take a peek or should we let Undo handle that?
@bertieb np. It's something that should be handled programmatically, not by having to rely on humans to notice.
@bertieb My original comment wasn't intended to be negative to you. While it's frustrating to see something reported a second time, it's not something that we humans should have to think about when reporting.
@Makyen Not taken as such, no worries; just felt silly for not catching it :) But as you say, it would be nice if a duplicate !!/report could be caught and not duplicated
@EriktheOutgolfer What I mean is that A) a post should not be re-reported without an edit changing the post. B) Shouldn't re-report for the exact same detections (i.e. exact same strings detected), even if edited. (B) is, obviously harder, and less of a priority.
@EriktheOutgolfer Yes, but even so, it shouldn't actually report it if it's the same version as was already reported, unless we have something like !!/report-force.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +5 more: Rapid Tone Diet by user90336 on workplace.SE
