Open egalano opened 5 years ago
Is this a bug with the library and how it is interpreting certain client's messages?
Maybe. That last example in the log 0167f758bdae
is 1546043047342
which as a unix timestamp is a few digits too many. I'd want to enable debug logging on the dht logger and see what the full message looks like. Maybe a specific client version is using the wrong timestamp format.