Difference between revisions of "Darkcanuck/RRServer/KnownIssues"
< Darkcanuck | RRServer
Jump to navigation
Jump to search
Darkcanuck (talk | contribs) (a known non-issue) |
Darkcanuck (talk | contribs) (updating issues) |
||
| Line 6: | Line 6: | ||
== Performance == | == Performance == | ||
| − | + | * '''Slow results upload''' This is primarily due to results being relayed to [[ABC]]'s server. Try uploading melee results (which are not relayed) to see the difference. | |
| − | * ''' | ||
| Line 17: | Line 16: | ||
== Resolved Issues == | == Resolved Issues == | ||
* '''Server not sending battle numbers or priority pairings after upload.''' Missed this one reading through the client code -- it's a bit cryptic, involves special brackets and doesn't get displayed by the client. '''Fixed!''' -- [[User:Darkcanuck|Darkcanuck]] 18:14, 27 September 2008 (UTC) | * '''Server not sending battle numbers or priority pairings after upload.''' Missed this one reading through the client code -- it's a bit cryptic, involves special brackets and doesn't get displayed by the client. '''Fixed!''' -- [[User:Darkcanuck|Darkcanuck]] 18:14, 27 September 2008 (UTC) | ||
| + | * '''Occasional slow page loads (or slow results upload).''' This is due to the ratings rebuild currently in progress and should clear up once the rebuild has caught up to current results. ''Rebuild finished about 1 week ago'' --[[User:Darkcanuck|Darkcanuck]] 07:22, 5 October 2008 (UTC) | ||
Revision as of 08:22, 5 October 2008
Navigation: About | Updates | Ratings | Query API | Roadmap | Design | Develop | Known Issues
If you find any bugs or run into any problems with the server, please report them on the discussion page. I'll put them here once I've had a chance to review. -- Darkcanuck
Performance
- Slow results upload This is primarily due to results being relayed to ABC's server. Try uploading melee results (which are not relayed) to see the difference.
Results Upload
- FAIL. Survival count should total 35 for roborumble. This check was added based on a suggestion by GrubbmGait to prevent melee results from being sent to the rumble results by a misconfigured client. But I believe this condition may also happen if both bots crash? I'm noticing a disproportionately large number from "ags.rougedc.RougeDC Classic" -- any ideas?
- I don't know of any cases of RougeDC Classic crashing. It certainly isn't crashing on my client. (Also: To me as author of RougeDC, it would be helpful if anyone sees it crash and details about it cashing). One note, is to my understanding the survival total may not add up as well when both bots die at the same time. I know of no reason that would happen with RougeDC more than any other bot, but it's another possible cause of survival total discrepancies. --Rednaxela 01:29, 27 September 2008 (UTC)
Resolved Issues
- Server not sending battle numbers or priority pairings after upload. Missed this one reading through the client code -- it's a bit cryptic, involves special brackets and doesn't get displayed by the client. Fixed! -- Darkcanuck 18:14, 27 September 2008 (UTC)
- Occasional slow page loads (or slow results upload). This is due to the ratings rebuild currently in progress and should clear up once the rebuild has caught up to current results. Rebuild finished about 1 week ago --Darkcanuck 07:22, 5 October 2008 (UTC)
