From 17efa721c8a8ee9af67cdd24636196acf30031cb Mon Sep 17 00:00:00 2001 From: Jonathan Warren Date: Sat, 30 Mar 2013 14:36:18 -0400 Subject: [PATCH] be verbose to help diagnose issue --- bitmessagemain.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/bitmessagemain.py b/bitmessagemain.py index 66e36d12..c33d8053 100755 --- a/bitmessagemain.py +++ b/bitmessagemain.py @@ -7,7 +7,7 @@ #Right now, PyBitmessage only support connecting to stream 1. It doesn't yet contain logic to expand into further streams. softwareVersion = '0.2.7' -verbose = 1 +verbose = 2 maximumAgeOfAnObjectThatIAmWillingToAccept = 216000 #Equals two days and 12 hours. lengthOfTimeToLeaveObjectsInInventory = 237600 #Equals two days and 18 hours. This should be longer than maximumAgeOfAnObjectThatIAmWillingToAccept so that we don't process messages twice. lengthOfTimeToHoldOnToAllPubkeys = 2419200 #Equals 4 weeks. You could make this longer if you want but making it shorter would not be advisable because there is a very small possibility that it could keep you from obtaining a needed pubkey for a period of time. @@ -375,7 +375,6 @@ class receiveDataThread(QThread): printLock.release() del self.objectsThatWeHaveYetToCheckAndSeeWhetherWeAlreadyHave[objectHash] else: - #print 'processData function making request for object:', objectHash.encode('hex') self.sendgetdata(objectHash) del self.objectsThatWeHaveYetToCheckAndSeeWhetherWeAlreadyHave[objectHash] #It is possible that the remote node doesn't respond with the object. In that case, we'll very likely get it from someone else anyway. break -- 2.45.1