Roborumble Bot Details Gives Server Error

Jump to navigation Jump to search

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.

Skotty (talk)23:38, 18 November 2013

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:LiteRumble/Roborumble Bot Details Gives Server Error/reply.

 

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.

Skilgannon (talk)09:16, 19 November 2013

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?

Beaming (talk)14:52, 19 November 2013

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.

Rednaxela (talk)16:33, 19 November 2013

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.

Skilgannon (talk)22:23, 19 November 2013
 
 

Thanks, Skilgannon. It's all good now.

Skotty (talk)16:42, 19 November 2013

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.

Skilgannon (talk)15:19, 21 November 2013