[spambayes-bugs] [ spambayes-Bugs-797890 ] Assertion errors from classifier for new messages

[SourceForge.net]

Bugs item #797890, was opened at 2003-08-30 19:37
Message generated for change (Comment added) made by richiehindle
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=797890&group_id=61702

Category: pop3proxy
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Anderson J. Vitous (avitous)
Assigned to: Nobody/Anonymous (nobody)
Summary: Assertion errors from classifier for new messages

Initial Comment:
Installed from CVS latest version as of 8/30/03 (1.0a4 
wouldn't work for me so reinstalled).  Python version is 2.
2.3 on Windows XP with latest pybsddb installed.  Trained 
with recent spam/ham collections (about equal numbers 
of messages, approx. 400 each), configured proxy.  Using 
Mahogany mail client pointed to pop3proxy (localhost).

Each new message retrieved results in an assertion 
failure:

AssertionError
Traceback (most recent call last):
  File "D:\apps\spambayes\pop3proxy.py", line 439, in 
onRetr
    evidence=True)
  File "D:\apps\spambayes\spambayes\classifier.py", line 
223, in chi2_spamprob
    clues = self._getclues(wordstream)
  File "D:\apps\spambayes\spambayes\classifier.py", line 
451, in _getclues
    prob = self.probability(record)
  File "D:\apps\spambayes\spambayes\classifier.py", line 
307, in probability
    assert hamcount <= nham

(from console running pop3proxy.py)

Also inserted into headers of each message:
X-Spambayes-Exception: exceptions.AssertionError() in 
probability() at
	D:\apps\spambayes\spambayes\classifier.py line 
307: assert
	hamcount <= nham


----------------------------------------------------------------------

>Comment By: Richie Hindle (richiehindle)
Date: 2003-08-30 20:01

Message:
Logged In: YES 
user_id=85414

This is a bug that's been cropping up from time to time,
but we haven't been able to reproduce it.  It sounds from
your description that you have a way to reproduce it - just
train on your corpuses and it fails straight away...?  If that's
true, could you attach your corpuses to this bug report?
Or if you've private messages in there, would you be willing
to send the corpuses to me directly?  I'd love to be able to
track this one down.

If you do send/attach your corpuses, please zip them up
to guarantee they don't get mangled by intermediate
mail/web servers.

How are you training?  Through the web, or on the command
line?  If on the command line, what is the exact command
you're using?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=797890&group_id=61702