[2024-07-08T15:10:46 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 754.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-07-08T15:23:37 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 771.4 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-07-08T15:26:07 UTC]: teward/Cerberus: main SE WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1680.0 seconds after connection; 177.2 seconds after heartbeat.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Mast That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
[2024-07-08T17:53:07 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 8969.1 seconds after connection; No heartbeats have been received on the current WebSocket.
@Ollie That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Fastnlight A normalized version, {{'2347066474917'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +234 706 647 4917 to determine which entries on the number lists match that pattern, which would tell you: Matched by +234-706-647-4917 on line 3052 of watched_numbers.txt: 2347066474917 found normalized
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-16: uduehiherbalcare Potentially bad keyword in title - Position 0-16: uduehiherbalcare Potentially bad keyword in username - Position 0-16: uduehiherbalcare
[2024-07-08T19:16:20 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4310.5 seconds after connection; 93.7 seconds after heartbeat.
[2024-07-08T19:38:19 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 6312.9 seconds after connection; No heartbeats have been received on the current WebSocket.
@ThomasWard Those are all SE WebSockets. All of them are failures on SE's side, either just randomly deciding to close the connection or not sending a heartbeat within the expected timeframe (which may or may not indicate the WebSocket is stuck). That the EditWatcher isn't getting any heartbeats (unless it's also showing a timeout) isn't a failure, it's just a reflection that the EditWatcher has a lot of subscribe/unsubscribe activity from SD's side.
@Makyen Note: that the non-receipt of a heartbeat when a heartbeat isn't needed isn't considered a failure and isn't reported as one, just included as part of the information with real failures (i.e., reports of exceptions).
[2024-07-08T19:48:07 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 587.0 seconds after connection; No heartbeats have been received on the current WebSocket.
I need to write up, yet another, MSE post about SE WebSocket issues (they affect regular SE pages too, not just SD). I've worked on a spreadsheet to better format the data that's available from the "Recovered from" reports that have been posted in here, but haven't written up the next MSE post, yet, as it didn't seem like it would be helpful to post it over the Fourth of July holiday, given that a substantial portion of the company were taking that off.
> Bad phone number in body, bad phone number in title, numbers-only title, phone number detected in body, phone number detected in title ---------- Bad phone number in body - +1-844-640-0543 found verbatim; 8446400543 found normalized Bad phone number in title - +1-844-640-0543 found verbatim; 8446400543 found normalized Numbers-only title - Position 0-15: +1-844-640-0543 Phone number detected in body - Position 1-15: 1-844-640-0543 Phone number detected in title - Phone number: 18446400543
@spe and @fast My standards are a little different, but I wanted to make sure before using a high priority flag.
Thanks.
@Spevacus Remember that while AI has its benefits, it’s essential to balance it with human creativity and expertise for a well-rounded content strategy.
No problem. Everyone has their own standards. There are many cases where I personally don't feel like the post deserves a red flag, despite other people believing it does (so I don't flag at all).
@Makyen If you're looking for examples for that post, Is it punishable to vote for re-opening own question? on MSO could have been caused by a websocket failure; my comment on that question notes that the timing of the delete vote relative to their reopen vote was not even close to what the user observed. Of course, it's impossible to say for sure what happened in that specific instance.
[2024-07-08T20:52:47 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 3879.7 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-07-08T21:02:50 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 270.0 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-07-08T21:16:54 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 843.7 seconds after connection; No heartbeats have been received on the current WebSocket.
> Numbers-only title, phone number detected in body, phone number detected in title ---------- Numbers-only title - Position 0-15: +1-833-266-7657 Phone number detected in body - Position 1-15: 1-833-266-7657 Phone number detected in title - Phone number: 18332667657
[2024-07-08T23:05:34 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 6520.1 seconds after connection; No heartbeats have been received on the current WebSocket.
