@YvetteColomb once again, sorry about that. When we implemented the reporter functionality we accidentally broke some stuff. As art said, I should be able to do some work on it tomorrow afternoon AUS time.
If you force push though don't you erase whatever you committed anyway? And the next time someone tried to pull, it would have a problem with it anyway.
But then the next time someone tries to pull, it wouldn't let them because GH HEAD wouldn't have bad commit. The bad commit would also still be visible on GH, just not linked besides in this room.
1. [:32962948] <processed without return value> 2. [:32962918] That message is not a report. 3. [:32962917] <processed without return value> 4. [:32962901] <processed without return value>
Backoff received of 10 seconds on request to questions/128850;128928?site=mathematica at 08:16:14 UTC
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: abrasive approaches of treating? by snedashelly on drupal.stackexchange.com
Couldn't get it working on EC2, so I'll just leave the PC on all day
FYI: Smokey is currently running on my server. Connectivity with metasmoke is OK, but the MS-Smokey websocket is down. The API feedback report messages will not work.
along with anything else that needs the websocket, such as preventing Tavern escalation
Smokey still updates it last seen timestamp, I wonder if we could rescue him with a autopull commit, but that fails because the is no metasmoke-smokey connection
Smokey still updates his timestamp in metasmoke too
