On Sun, 21 Feb 2010 14:29:47 -0500, "W. Trevor King" <wk...@drexel.edu> wrote: > On Sun, Feb 21, 2010 at 09:52:28AM -0800, Nicolas Pouillard wrote: > > On Sun, 21 Feb 2010 08:42:49 -0500, "W. Trevor King" <wk...@drexel.edu> > > wrote: > > > On Sun, Feb 21, 2010 at 08:38:35AM +0200, Tero Tilus wrote: > > [...] > > > > Have a pointer to code? > > > > > > My code is currently stuffed into an in-transition BE project, but it > > > should be easy to separate. Grab the whole repo with Bazaar: > > > bzr branch http://www.physics.drexel.edu/~wking/code/bzr/be.mailing-list > > > Graphing module is libbe/util/graph.py. My very minimal browser is > > > misc/mailbox-tools/mailgraph.py. Set up the BE version file with > > > cd be.mailing-list > > > make libbe/_version.py > > > and run the browser with > > > misc/mailbox-tools/mailgraph.py *.mbox > > > Press 'h' for help. > > > > I've tried your program on a 100 messages mbox and got this: > > > > missing Message-ID: <HIDDEN> > > ... > > You probably had a bunch of emails in you mbox with > In-Reply-To: <HIDDEN> > But no message(s) with > Message-ID: <HIDDEN> > > If mailgraph.py can't find the parent message, it prints that warning > and continues, so you can probably just ignore it. > > > Traceback (most recent call last): > > ... > > libbe.util.graph.CyclicGraph: 3 of 100 elements not reachable from tips > > You have a cyclic reference in your mbox somewhere. I've added some > really inefficient code to actually *find* cycles (rather than just > deducing their existence) and print useful error messages. Pull my > current repo and try: > > $ misc/mailbox-tools/mailgraph.py --check-for-cycle *.mbox > > Then you'll have to go through the mbox (or a copy) by hand and break > the cycle. The check only finds one cycle at a time, so you may need > to iterate...
I get: ... libbe.util.graph.CyclicGraphError: cycle detected: Sun, 21 Fe Reinier Lamers [darcs-users] [patch167] Reintroduce UTF-8 tagging... Sun, 21 Fe Reinier Lamers [darcs-users] [patch167] Reintroduce UTF-8 tagging... Actually the mentioned mail have Message-ID equals to In-Reply-To. While I'm reporting this issue and thus won't get any such messages, it would be "nice" to have a more robust behavior in case of cycles. In particular these auto-cycles can be just ignored. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
