teward/Osiris: In getting MS post information, recovered from `requests.exceptions.JSONDecodeError: [Errno Expecting value] <html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html> : 0`
teward/Osiris: In getting MS post information, recovered from `requests.exceptions.JSONDecodeError: [Errno Expecting value] <html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html> : 0`
@Spevacus A normalized version, {{'971585391570'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number +971 585391570 to determine which entries on the number lists match that pattern, which would tell you: Matched by +971585391570 on line 3061 of watched_numbers.txt: 971585391570 found normalized
@Spevacus 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.
teward/Osiris: In getting MS post information, recovered from `requests.exceptions.JSONDecodeError: [Errno Expecting value] <html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html> : 0`
@ThomasWard If you're around, it looks like MS is having issues. I'm getting "503 Service Unavailable No server is available to handle this request." when trying to access it and Osiris appears to be having problems reaching it too. So, it could probably use a kick.
