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
Problem is the fix to #12, which breaks logging on any IPv6 addresses since they are colon-separated hex numbers and results in an exception like (on postgres):
psycopg2.errors.InvalidTextRepresentation: invalid input syntax for type inet: "2604"
I am working on a PR to fix this which I should have ready shortly. I am filing this issue in case someone googles that exception. And unfortunately this means that since that fix, anyone using this has been missing out on logs from any IPv6 addresses...
The text was updated successfully, but these errors were encountered:
cjh79
added a commit
to cjh79/drf-api-tracking
that referenced
this issue
Jun 19, 2020
Problem is the fix to #12, which breaks logging on any IPv6 addresses since they are colon-separated hex numbers and results in an exception like (on postgres):
psycopg2.errors.InvalidTextRepresentation: invalid input syntax for type inet: "2604"
I am working on a PR to fix this which I should have ready shortly. I am filing this issue in case someone googles that exception. And unfortunately this means that since that fix, anyone using this has been missing out on logs from any IPv6 addresses...
The text was updated successfully, but these errors were encountered: