[2024-06-27T15:15:26 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4985.6 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-06-27T17:36:39 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 17516.2 seconds after connection; 147.4 seconds after heartbeat.
[2024-06-27T17:55:22 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 1122.8 seconds after connection; 522.1 seconds after heartbeat.
[2024-06-27T18:09:03 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 10416.9 seconds after connection; No heartbeats have been received on the current WebSocket.
@SmokeDetector Translation: If there is a run out in the middle of an over then who will be on strike? Looks like a copy of the title, guess this is naa at least
@JeffSchaller A normalized version, {{'7070752663'}}, 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 7070752663 to determine which entries on the number lists match that pattern, which would tell you: Matched by 7070.752.663 on line 4421 of watched_numbers.txt: 7070752663 found normalized
[2024-06-27T19:22:48 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2269.9 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-06-27T19:51:28 UTC]: teward/Cerberus: main SE WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 3995.1 seconds after connection; 87.0 seconds after heartbeat.
[2024-06-27T20:31:48 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4885.3 seconds after connection; 131.0 seconds after heartbeat.
[2024-06-27T20:42:52 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 4804.5 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-06-27T21:38:03 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 3311.0 seconds after connection; No heartbeats have been received on the current WebSocket.
@Machavity Please provide an adequate reason for rejection (at least 20 characters long) so the user can learn from their mistakes. Use -force to force the reject
hence my suggestion of maybe having the watch command check for open PRs. not sure how much work that would involve but i think a few people have considered thinking about the problem
@Fastnlight similar idea, but my idea is if i were to watch a link, it would warn me there is an open pr with the number. that way i could instead approve the PR
@Vickel honestly wouldnt surprise me. they have scripts for everything :P
honestly, if an approved blacklister tries to watch something with an open PR, it could just auto approve the PR. though that would probably take a tad extra work
[2024-06-27T23:28:09 UTC]: teward/Cerberus: EditWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 6605.4 seconds after connection; No heartbeats have been received on the current WebSocket.
[2024-06-27T23:45:59 UTC]: teward/Cerberus: DeletionWatcher WebSocket: Recovered from websocket._exceptions.WebSocketConnectionClosedException: Connection to remote host was lost. 2963.5 seconds after connection; 91.0 seconds after heartbeat.
