Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on nil"
Date: Fri, 14 Mar 2008 11:51:31 -0700	[thread overview]
Message-ID: <1205520291-sup-7442@south> (raw)
In-Reply-To: <1205210652-sup-1364@amethyst>

Reformatted excerpts from Alexandra Walford's message of 2008-03-10:
> I am getting frequent sup crashes with "wrong id called on nil" (using
> the latest git master), when thread_by_subject is true.

The thread_by_subject stuff is broken and I have a patch to fix it, I
just haven't merged it in yet. I'll try and do this soon. In the mean
time, as you've discovered, turning off thread_by_subj is the
workaround.

-- 
William <wmorgan-sup at masanjin.net>


  parent reply	other threads:[~2008-03-14 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  4:45 Alexandra Walford
2008-03-11  7:06 ` Christopher Warrington
2008-03-12  0:51   ` Michael Gurski
2008-03-14 18:51 ` William Morgan [this message]
2008-03-14 22:28   ` Alexandra Walford
2008-03-17 16:41   ` William Morgan
2008-03-18 12:35     ` Alexandra Walford

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=1205520291-sup-7442@south \
    --to=wmorgan-sup@masanjin.net \
    /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