Older stats issue

[gopher_yarrowzoo]

Ya that is a problem when you upgrade
I guess that's why I still have my 1st wife
Just to much work getting it all back right

That and you probably can't afford the divorce and keep the pharm.

[LAURENU2]

That and you probably can't afford the divorce :P and keep the pharm.

[gopher_yarrowzoo]

Ha Ha Ha Ha Ha Ha Ha Ha Ha sorry dude you walked into that one..
I mean do you get this one, Woman walks on her husband 10 yrs ago they did have a kid together - he is paying maintenance and gets access to the kid...
roll forward to today, he wins 26 million on the euro lottery, he was going to give her 1 million of it, she didn't think that was enough so took him to court got 2 million and the maintenance up'd to 2,000 a month...
Yeah she walked out on him for someone else.

[Paratima]

Thanks for the quick fix on the "Hosts" problem. It really helps when we can see what the individual units are producing.

Have a question: I was just checking on my progress in Docking and the numbers were a bit strange. It's likely just a quirk in the updating process - Docking's server has been up and down like a wild yo-yo the last couple of weeks. Anyway, I looked at the Update times in the upper right corner and found the following:

Docking@Home - Free-DC Overview
Last Checked : Fri Nov 26, 14:38:29 2010 EST
Data Updated : Fri Nov 26, 11:42:37 2010 EST
Current Time : Fri Nov 26, 13:07:11 2010 EST

According to my system clock, it was around 13:10 when I made the check. Plenty of slop in clocks to account for the difference on Current Time. However, I got to wondering about the "Last Checked" time. Does the server actually reach ahead an hour and a half to get the upcoming stats? If so, I'd like to suggest a stock market application for that piece of code. You could have a real winner here!

[Bok]

We think there is a bug in the timezone code somewhere. The dates held in the database are based on EST time as that is where the box is, but when it shows it it attempts to convert it to a localtime but it's going wrong. Might just revert this to using UTC at somepoint perhaps. It's gopher's baby though so I'll lte him take a look first. (perhaps we had some hacks in the tz code that didn't come over from the old box? )

[Paratima]

Pooh! I thought you were onto something really good in the Predictive Computing area! Oh, well. If it's just a TZ error, then it's a small one. If you do decide to get into PC, let me know!

[gopher_yarrowzoo]

Hmm okay I'll have a look at it. I did do a few code changes back and forth to get it work, I guess it broke...

AH found the problem - had to set the TZ to a custom one since it just wouldn't behave since AZ doesn't do DST but the server kept thinking it did.. fixed line removed and tested working - porting to live or I will as soon as it allows me to