Thread history
Viewing a history listing
| Time | User | Activity | Comment |
|---|---|---|---|
| 23:38, 18 November 2013 | Skotty (talk | contribs) | New thread created | |
| 02:11, 19 November 2013 | Beaming (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 09:16, 19 November 2013 | Skilgannon (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 14:52, 19 November 2013 | Beaming (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 16:33, 19 November 2013 | Rednaxela (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 16:42, 19 November 2013 | Skotty (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 22:23, 19 November 2013 | Skilgannon (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
| 15:19, 21 November 2013 | Skilgannon (talk | contribs) | New reply created | (Reply to Roborumble Bot Details Gives Server Error) |
I've been getting Server Error whenever trying to see details or do a comparison with game=roborumble. It works fine for other game types.
I think roborumble just do it more often. I notice the correlation with stats upload time. At least right around when my client uploads data it gives this error. May be CPU cycles taken for stats recalculation.
I've just fixed a bug where removing a bot would corrupt the rankings list (it was still storing it in an old format - gah!) until another battle was uploaded and processed, which saved it in the new format. This should fix the problem.
One more thing I noticed, once I retire a bot. I see them both new and old one in rating for quite a while. Is it related to the fixed bug?
That's a longstanding-ish normal thing. IIRC, to keep clients from fighting over removing/readding bots, I think the server doesn't remove bots until a certain amount of time since the last upload for that bot.
LiteRumble doesn't do that, the moment a client requests a bot to be removed it removes it. However, it keeps all the pairing data against it for 365 days in case it is re-added so that battles don't have to be re-run.
I'm guessing the delay was due to a client taking a while to re-download the participants page.
I actually don't think that's what the issue was, I've fixed another bug in the priority battles generation which will give more weight to bots that are missing more pairings. I've also got a lot more debugging so I can see what is happening if this pops up again.
