Something wrong with TIMER [FIXED]

"

Jonathan wrote:

"

[22:05:18] Dylan: so, good and bad news
[22:05:22] Jonathan: go on
[22:06:18] Dylan: well, i see the bug, but it turns out it is DST related, and it seems as though the dates i'm storing in postgres aren't utc
[22:06:33] Jonathan: oh yeah
[22:06:34] Jonathan: DST
[22:06:35] Jonathan: Hah
[22:06:38] Jonathan: Of course
[22:06:43] Dylan: yeah :S
[22:07:48] Dylan: so yeah, i mean, that problem is solveable, but something is wrong with the configuration, or how i'm using dates
[22:07:53] Jonathan: Right
[22:07:57] Dylan: because i intented everything to be utc

Looks like we have made a minor mistake with how dates are being stored with regard to the timer. Because we are out of the "hole" if we restart the thing now it should work as normal.

As a side note, it looked like about 100 extra people were invited during the period that it was behaving badly.

"

Nuzzgrumble wrote:

I think I was in those 100, because i just woke up and I have been invited. Never expected it will be so soon.

"

Gman666 wrote:

COME on the Key !!
this is like Loto its Not going to happen is it :-/

"

Jonathan wrote:

As a side note, it looked like about 100 extra people were invited during the period that it was behaving badly.

"

Jonathan wrote:
As a side note, it looked like about 100 extra people were invited during the period that it was behaving badly.