On Wed, Feb 05, 2020 at 12:50:13AM +0100, Sander Steffann wrote:
> Hi,
>
> > I submitted an issue about this on github, but it was more to do with an
> > inconsistency between using localtime in the local database and UTC coming
> > from PDB. This is not the first time I have encountered timezon
Hi,
> I submitted an issue about this on github, but it was more to do with an
> inconsistency between using localtime in the local database and UTC coming
> from PDB. This is not the first time I have encountered timezone related bugs
> with the Python PDB modules. Which database are you using
?
From: Pdb-tech on behalf of Sander
Steffann
Sent: Tuesday, February 4, 2020 3:20:44 PM
To: pdb-tech@lists.peeringdb.com
Subject: Re: [PDB Tech] Clock skew?
Hi,
> There seems to be a problem with the clock on the server. I am seeing updated
> timestamps
Hi,
> There seems to be a problem with the clock on the server. I am seeing updated
> timestamps in the future after a sync:
Never mind, it turns out that the django_peeringdb module is doing weird things
with time zones. It stores them with a weird offset in the database.
Anyway, not a server
Hi!
There seems to be a problem with the clock on the server. I am seeing updated
timestamps in the future after a sync:
peeringmanager=# select id,name,status,created,updated from
peeringdb_organization where updated>CURRENT_TIMESTAMP order by updated desc;
id | name
