Good news: I've fixed some defects with the Popular Buys (aka Stats by Cards) function. It should no longer give "internal server error" if you search for a specific player name.
In the near term, it will still give out somewhat incorrect information. If you have looked carefully, you may have noticed that the
win rate with/without columns are invalid. This also throws off the player-specific
effect with/without columns. In the next hour, that should (hopefully) start to change as I kick off a process that will recalculate the effects of buys over the 9.2M game history. I anticipate this process will take ~12 hours to complete. I'm a bit uncertain what will happen to the site while the recalc is underway... There's a reasonably good chance it will have no impact, but please do let me know if you see new problems crop up, like, for example, pages that previously worked becoming really slow.
This will delay the load of the data from today (2012-12-21) until tomorrow morning US-time.
On other defects... No real progress on these others, but here is what I know:
When I look at a player's page and click on "Record by Opponent" it always times out on me. I tried a few other players other than myself.
It could be just with players who have a longer history.
This is logged in the issues list as
https://github.com/mikemccllstr/dominionstats/issues/26. David Lu implemented some code that dramatically helped the /player page itself. We probably need to take a look at how to take advantage of it with the /games_by_opponent page. So this might be close, but right now it is dependent on how many games have been played by the player being searched.
Whenever I look at an isotropic log hosted on Councilroom, I don't see the graphs of the score and money, just blank spaces next to the words "score" and "money" (surprisingly). The list of goals achieved (and their associated graphics) seems to be doing just fine, though.
This is logged in the issues list as
https://github.com/mikemccllstr/dominionstats/issues/28. It is known, but I'm not sure what it will take to fix it. The conversation in the other thread is helpful to elaborate on where it might be working and where not.
Mike