[18:57:14] phuzion: I know, I just wanted to put my dev account to use somwhat and be helpful [18:58:32] Yoshi24517: Honestly, what we could use right now is probably a rewrite of es2r.py if you are able to do that. Or just identify/fix the bug. [18:58:54] phuzion: es2r.py? [18:59:34] Yoshi24517: https://github.com/huggle/XMLRCS/blob/master/src/es2r/es2r.py [19:00:13] phuzion: Describe the problem/bug as best you can [19:01:28] Yoshi24517: We haven't been able to reliably reproduce the bug, but in essence, es2r.py hangs inexplicably, and that's what causes XMLRCS to have nothing in it, and causes Huggle to fail back to IRC. [19:03:40] i do know the error that pops up on huggle itself, and that is that redis is empty for more than 10 seconds [19:03:47] imma look around in that [19:03:50] Right [19:04:00] es2r is the script that takes data from eventstreams and feeds it into redis. [19:04:19] Without es2r running, redis empties, and xmlrcs has nothing to feed to huggle. [19:09:58] hmmmmm [19:16:38] Yoshi24517: My recommendation is to set up an environment with a full xmlrcs environment. Redis, xmlrcsd, es2r, etc, and start breaking things. Cause network drops, kill processes, make things hang, etc. There's bound to be a good handful of bugs that you could easily find and fix. [22:15:34] phuzion: I have a theory that it may be a server side issue, because in T179986 when it happened our eventstream 502'd. That my not be the case here, but next time it happens [22:15:51] Another thing is watch memory. If its running low on memory it may close the connection causing redis to be empty [22:16:51] but essentially watch for errors the next time it happens [22:19:16] Also, what are the specs of the xmlrcs server if you know them