Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Nicolas Pouillard <nicolas.pouillard@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>,
	Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] email threading - tree vs. graph
Date: Mon, 22 Feb 2010 06:00:53 -0800 (PST)	[thread overview]
Message-ID: <4b828e15.0e67f10a.21cd.ffffc19d@mx.google.com> (raw)
In-Reply-To: <20100221192947.GA16075@mjolnir>

On Sun, 21 Feb 2010 14:29:47 -0500, "W. Trevor King" <wking@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" <wking@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


  reply	other threads:[~2010-02-22 14:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 11:49 W. Trevor King
2010-02-21  6:38 ` Tero Tilus
2010-02-21 13:42   ` W. Trevor King
2010-02-21 17:52     ` Nicolas Pouillard
2010-02-21 19:29       ` W. Trevor King
2010-02-22 14:00         ` Nicolas Pouillard [this message]
2010-02-22 15:54           ` W. Trevor King
2010-02-22 16:04             ` Nicolas Pouillard
2010-02-22 16:48   ` W. Trevor King
2010-02-23 10:29     ` Nicolas Pouillard
2010-05-25 18:50   ` W. Trevor King
2010-06-03  4:27     ` Rich Lane
2010-06-03 10:21       ` W. Trevor King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4b828e15.0e67f10a.21cd.ffffc19d@mx.google.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox