|
As a follow-up to Scheduled Downtime, everything went very well (knock on wood) with tonight's update. We were down for a very short time (about 20 minutes), and there weren't any errors during the update.
This was an important update, but it's pretty much free of new features. There were numerous changes to how games are represented in the database and on the filesystem. These changes will be important for future releases, but, for now, I'll just be happy if everything continues working as before.
During the update, I converted about 3,200 games from the old format to the new format. This should cover all active games, and anything you can find in the archives. However, there are about 22,000 games that are still in the old format. I'll be updating these periodically, in the background, over the next week or so.
If you come across any problems with any games (or anything else), please post on the forums or contact me via email.
Bug Fixes
While this release is short on new features, there were several bug fixes. Among them:
The focus bug in Footsteps has been fixed. This was a fairly major bug, though it didn't strike very often. If your opponent bid while you were in the process of selecting your bid, the page would update and your bid would be reset to 1. If you didn't notice and hit the bid button at that moment the accidental bid of 1 would go through. This bug could not occur in games versus bots, and it would only strike in games being played in realtime. So, while I don't believe this effected too many people or games, I've very glad it's fixed now.
The multiple rematch bug has been fixed. This was a hard one to fix. All the logic for determining whether or not display the "Request a Rematch" button was correct. But, because of ActiveRecord caching, the logic would operate on old data in one case. If both players had already agreed to a rematch, the "Request a Rematch" button would re-appear after the final move, but only for the player who moved last. If the page were refreshed, the cache would be cleared and the button would then disappear again. As a result, sometimes two rematches could be requested and started. The fix was to dump the cached data after the final move of the game.
The Safari page scrolling bug has also been fixed. If you're curious, there's more about here: Games not working on Safari 2?.
That's it for now. Look for more new features later this week.
|
