Re: [PDB Tech] Peeringdb sync problem

i think this one is caused by using Dango3. you should install Django < 3 Sent from my iPad On May 22, 2020, at 8:19 AM, "jan.boog...@swisscom.com" wrote:  Hi Stefan I upgraded now to python3 and have new errors, I tried with python3.6.9 and 3.8.3: pdb@pdb2:~$ peeringdb sync Syncing to

Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

in a while. That being said, there was discussion about switching to peeringdb-py/django_peeringdb in Peering Manager but until django_peeringdb supports Django3 it is a non-starter. From: Brian Dickson Sent: Friday, May 15, 2020 4:33:34 PM To: Milton Ngan Cc: Chris

Re: [PDB Tech] [External Mail] Re: Problem doing initial 'peeringdb sync', foreign key constraint fails?

I replicated the problem and added some additional debugging to illustrate the problem. The first time stamp is what is in the object and is in UTC, the second is the UTC timestamp for now, and the third is the local timestamp. You can see that the update time is in the "future" by about 37

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

If you are situated West of UTC you might be running into the timezone issue I reported. The work around I had was to change this line in peeringdb/_update.py from

Re: [PDB Tech] peeringDB Python Module Issues with Python 3?

The only issue I had was with django-peeringdb needing to use Django < 3.x. A whole bunch of things don’t work with the latest version of the framework. I had to put this requirement into my python projects that used the django-peeringdb module and PY3. Django<=2.2.9 > On Feb 11, 2020, at

Re: [PDB Tech] Clock skew?

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?

[PDB Tech] Initial sync failing with PeeringDB Python module

I have noticed that the "peeringdb sync” command will fail to sync one of the tables when doing a full sync, or a large incremental sync. This is because while you are syncing one of the “base” tables, the dependent tables could be updated. So when you sync the dependent table, it may include

Re: [PDB Tech] Network does not exist error

I think this is the bug I reported recently. Update your python modules and do a full resync. It is the Django module in particular that causes the problem. There was an issue with time zone handling which would cause gaps in your data every time you synced. Sent from my iPad On Jun 2, 2017,