Closed j-f1 closed 7 years ago
Thank you for posting this issue.
Developers/Troubleshooters/Users of Smokey/Bug Causers:
Due to the nature of this bug and our difficultly in reliably replicating it, we need to keep this issue updated with a few key details when the issue occurs. Hopefully this will help us track down the bug directly or a pattern we can use to replicate the issue:
!!/report
was run or the last time Smokey posted a message?Also include a link to what you reported, so we can see if it's an issue with odd characters or such in the reported item's content that could have broken the chat socket or something. (As well, any additional information you can provide could be useful as well).
Note that we did some testing on this to try and replicate the chat failure with a debugger attached and couldn't replicate the failures that we've seen.
Since spam posts usually get deleted quickly, you might want to inline them like this:
Code:
<details><summary><a href="//charcoal-se.org">Post Link</a></summary>
> Post contents
</details>
Failure:
Success:
Reporting from FDSC doesn't seem to work either. Is that related to this, or is that solely a MS-FDSC thing?
Reporting from FDSC doesn't work for me either. I flagged a post today as rude, but till I noticed that it was not reported it was already gone.
Check on MetaSmoke to make sure your report didn't reach there - it's possible Smokey isn't reporting but MS is actually receiving the report.
I have checked, but it didn't reach MS either.
On 4 March 2017 at 11:37, Thomas Ward notifications@github.com wrote:
Check on MetaSmoke to make sure your report didn't reach there - it's possible Smokey isn't reporting but MS is actually receiving the report.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Charcoal-SE/SmokeDetector/issues/565#issuecomment-284143290, or mute the thread https://github.com/notifications/unsubscribe-auth/AXeJRsCgjkZGKgbA5SAtM9vJupv_xO3rks5riT8CgaJpZM4MSWW2 .
@teward Metasmoke doesn't store anything from manual report requests, it just passes them along to Smokey. You wouldn't see a post record being created, ever, if it isn't reported to chat.
Failure:
[**Apkzonar**][1] is also a good play-store alternative. I think It have a much bigger app and game selection . I've been using it for some time. There I have never had problems with malware, viruses.
- Chat message: http://chat.stackexchange.com/transcript/message/35837708#35837708
- Time: approx 10:13am UTC
- Last known alive time: directly beforehand (used !!/alive)
Success:
I think the second is good choice. Example: Is there anyone working in civil engineering outsourcing services in US
Here is another !!/report for a StackApps question which didn't break Smokey.
2 Successes:
Success:
Failure:
The report did not appear in either Metasmoke or SOCVR.
Failure:
Site: superuser.com
Content:
There exists a tool named SetDeliveryTime aimed to solve exact this issue. The tool is free for personal non-commercial use.
Chat message: http://chat.stackexchange.com/transcript/message/35866676#35866676
Time: approx 15:36 UTC
Last known alive time: directly beforehand (used !!/alive)
@NobodyNada may have just fixed this in #568 - see discussion there. TL;DR is that we weren't releasing the lock on the API in some cases, and we have metasmoke stats that back up that theory.
Success:
ghfhfhghghgghgjxdbfsbdfuidbnfeduifbnsuifhsdjifsud9hnfjbugtgggggg
I think that since we haven't hit a lockup in 3 days, we can safely assume the API locking issue was the cause. Closing.
Sometimes, Smokey will silently die when
!!/report
is called. This does not happen every time, and Smokey doesn’t restart or reply to the message. This seems to happen more frequently when!!/report
ing Ask Ubuntu questions.