You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't dug up the cause of this yet, but we found that when fetching a VLAN whose name is a number, the 'name' attribute comes back as an IPRecord. No such issue with any vlan whose name is a string or > 255.
This also appears to happen with 'description' and perhaps other attrs, but those are the two we found. It also appears to happen before serialization as we get an IPRecord for the attr before calling serialize().
Upon fetching a vlan whose 'name' and description are both '60', we got this:
Version: 3.4.5
I haven't dug up the cause of this yet, but we found that when fetching a VLAN whose name is a number, the 'name' attribute comes back as an IPRecord. No such issue with any vlan whose name is a string or > 255.
This also appears to happen with 'description' and perhaps other attrs, but those are the two we found. It also appears to happen before serialization as we get an IPRecord for the attr before calling serialize().
Upon fetching a vlan whose 'name' and description are both '60', we got this:
From
print(type(vlan.name))
After serializing:
The text was updated successfully, but these errors were encountered: