GettingStarted (How to install and run mail-trends) Wiki page commented on by greg.merideth
- Ubuntu 8 (2.6.27-7) stalls at 8000/14187 messages. Ran several times, each with same result. Last run, I let it sit for two hours in its own windows before breaking.
Ubuntu 8 (2.6.27-7) stalls at 8000/14187 messages. Ran several times, each with same result. Last run, I let it sit for two hours in its own windows before breaking.
Aug 18, 2009
GettingStarted (How to install and run mail-trends) Wiki page commented on by lpicanco
- Wish it worked through a proxy [2]
Wish it worked through a proxy [2]
Jul 31, 2009
GettingStarted (How to install and run mail-trends) Wiki page commented on by BUGabundo
- Hi.
How can I just check email from a special label like Trash or Spam?
Hi.
How can I just check email from a special label like Trash or Spam?
GettingStarted (How to install and run mail-trends) Wiki page commented on by drewbenn
- If you are getting the 'maximum recursion depth exceeded' (in len(c)) error, you could try this patch, which is how I bypassed that error:
{{{
--- a/mail-trends/jwzthreading.py 2008-03-26 05:53:42.000000000 -0700
+++ b/mail-trends/jwzthreading.py 2009-07-17 21:19:47.000000000 -0700
@@ -48,11 +48,14 @@
return True
return False
- def __len__(self):
- count = 1
- for c in self.children:
- count += len(c)
- return count
+ def __len__(self, sum=1):
+ count = 1
+ if sum > 332:
+ print 'uh oh reached 332!'
+ else:
+ for c in self.children:
+ count += c.__len__(sum + 1)
+ return count
def uniq(alist):
set = {}
}}}
It's a workaround, not a real fix, and I think you will end up with some bad/missing/incomplete data, but you will at least end up with viewable results. I don't know exactly what that is counting, but I hit that limit 21 times in ~40k messages. You might need a different value than 332 (for reference, I am running Python 2.6.2 in Ubuntu 9.04 64-bit with 2GB of RAM); I picked that value by counting how many lines deep the stack trace was when I ran mail-trends without this patch.
If you are getting the 'maximum recursion depth exceeded' (in len(c)) error, you could try this patch, which is how I bypassed that error:
{{{
--- a/mail-trends/jwzthreading.py 2008-03-26 05:53:42.000000000 -0700
+++ b/mail-trends/jwzthreading.py 2009-07-17 21:19:47.000000000 -0700
@@ -48,11 +48,14 @@
return True
return False
- def __len__(self):
- count = 1
- for c in self.children:
- count += len(c)
- return count
+ def __len__(self, sum=1):
+ count = 1
+ if sum > 332:
+ print 'uh oh reached 332!'
+ else:
+ for c in self.children:
+ count += c.__len__(sum + 1)
+ return count
def uniq(alist):
set = {}
}}}
It's a workaround, not a real fix, and I think you will end up with some bad/missing/incomplete data, but you will at least end up with viewable results. I don't know exactly what that is counting, but I hit that limit 21 times in ~40k messages. You might need a different value than 332 (for reference, I am running Python 2.6.2 in Ubuntu 9.04 64-bit with 2GB of RAM); I picked that value by counting how many lines deep the stack trace was when I ran mail-trends without this patch.
Jul 03, 2009
GettingStarted (How to install and run mail-trends) Wiki page commented on by diegoshalom
- "maximum recursion depth exceeded" SOLVED.
Just add a code "sys.setrecursionlimit(XXXX)" next to the left margin, previous to the code "opts = GetOptsMap()" (line ~249 of main.py). Replace XXXX with a large number. The default value is 1000 ("print sys.getrecursionlimit()"). I have 14K messages and I used XXXX=15000 successfully.
Hope it helps.
"maximum recursion depth exceeded" SOLVED.
Just add a code "sys.setrecursionlimit(XXXX)" next to the left margin, previous to the code "opts = GetOptsMap()" (line ~249 of main.py). Replace XXXX with a large number. The default value is 1000 ("print sys.getrecursionlimit()"). I have 14K messages and I used XXXX=15000 successfully.
Hope it helps.
