Hi,
Thank you for bringing this to our attention, i have opened a github
ticket for it here:
https://github.com/peeringdb/peeringdb/issues/68
Stefan
On 09/09/16 17:29, James Bensley wrote:
Hi All,
When using the API to look at a random network I see a possible
difference in behavior
The one situation that comes to mind that would cause what you are
describing is if you are running an older version of django-peeringdb
and it's failing validation on some of the enum fields that had values
added to them - e.g. they are valid on the server, but not valid locally
- which would
ist.py:267: UserWarning: Unknown
distribution option: 'test_requires'
warnings.warn(msg)
error in django-inet setup command: 'install_requires' must be a string or
list of strings containing valid project/version requirement specifiers
--------
Comman
We have deployed bug-fix release 2.7.2 and the issue should now be fixed.
Thanks again for the report, and apologies for the inconvenience.
Stefan.
On 18/01/2018 23.26, William Marantz wrote:
Hi Tech Team,
I've had code running for over a year now without issue that just
stopped returning
Looking into this, able to reproduce.
Not an intended change by any means, looks like something might be
broken with netixlan?name filter.
Will create github ticket and followup once i know more.
Stefan
On 18/01/2018 23.26, William Marantz wrote:
Hi Tech Team,
I've had code running for
I've made the appropriate ticket to track this issue at
https://github.com/peeringdb/peeringdb/issues/274
Thanks for your report, as this is an API bug, i will inquire about
getting it fast tracked for a bug fix release asap.
Stefan
On 18/01/2018 23.26, William Marantz wrote:
Hi Tech
ital :)
On 28/01/2020 14.13, Elmar K. Bins wrote:
Hi Stefan,
ste...@20c.com (Stefan Pratter) wrote:
PUT needs you supply values for all required fields not just fields you want
to change, i am guessing that's what is the issue here.
Thanks for the insight; I tried submitting the entire objec
PUT needs you supply values for all required fields not just fields you
want to change, i am guessing that's what is the issue here.
If you check the content of the 400 response you are getting it should
tell you which other fields it wants you to submit in your payload (or
any other reason
/2020 14.48, Elmar K. Bins wrote:
Hi Stefan,
ste...@20c.com (Stefan Pratter) wrote:
print(r.json())
Ah, I've been looking for that; now it just tells me...
{'meta': {'error': 'JSON parse error - Expecting value: line 1 column 1 (char
0)'}}
Ok, I've now tried putting data=...:
- Only
Validation errors are often (not always) caused by the server's
django-peeringdb version being ahead of your locally installed version.
In other words the server treats something as valid, while the client
doesn't.
What's the output of
`pip freeze | grep django-peeringdb`
and if its < 2.0
super().contribute_to_class(cls, name)
TypeError: Error when calling the metaclass bases
super() takes at least 1 argument (0 given)
pdb@pdb2:~$
Best regards
Jan
*Von:* Pdb-tech im Auftrag von
Stefan Pratter
*Gesendet:* Freitag, 22. Mai 2020 15:18
*An:* pdb
11 matches
Mail list logo
