Open F483 opened 8 years ago
Unfortunately the only way to know is to dump out the values to be stored as they come in, otherwise nothing is known until its too late.
I added a fix that only allows printable ASCII characters and converts everything else to hex before displaying it in the log. Should avoid having strange unicode characters messing everything up for store requests.
self.log.debug("setting '%s' = '%s' on network" % (safe_key, safe_value))
Was blindly printing binary.
Looking forward to using it, beautiful.
@robertsdotpm you made a pull request for the fix to the wrong repo. My repo only has the python 3 port so I would rather not mix anything in accept that.
Upstream pull requests should go here https://github.com/bmuller/kademlia/
I will also make some unit tests to handle all sorts of input for the DHT and see if I can find the bug.
Thanks. I've submitted a pull upstream. Hopefully it gets accepted
duplicate at https://github.com/Storj/dataserv-client/issues/188
This may be an upstream kademlia big as the last output comes from here https://github.com/bmuller/kademlia/blob/master/kademlia/network.py#L152
However without additional info its very hard to tell what happend as the log cuts off at exactly the part we need (the respective key value pair).