<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
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? Postgres?
<div><br>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Pdb-tech <pdb-tech-bounces@lists.peeringdb.com> on behalf of Sander Steffann <sander@steffann.nl><br>
<b>Sent:</b> Tuesday, February 4, 2020 3:20:44 PM<br>
<b>To:</b> pdb-tech@lists.peeringdb.com<br>
<b>Subject:</b> Re: [PDB Tech] Clock skew?</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
> There seems to be a problem with the clock on the server. I am seeing updated timestamps in the future after a sync:<br>
<br>
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.<br>
<br>
Anyway, not a server problem<br>
Sander<br>
<br>
</div>
</span></font>
</body>
</html>