Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: Steven Walter <stevenrwalter@gmail.com>
Cc: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Recovering a busted ferret db?
Date: Mon, 02 Nov 2009 03:53:39 -0800	[thread overview]
Message-ID: <1257162594-sup-7077@masanjin.net> (raw)
In-Reply-To: <e06498070911011203s66ece542mac80378442073369@mail.gmail.com>

[cc'ing list]

Reformatted excerpts from Steven Walter's message of 2009-11-01:
> Hooray, that worked.  There is an email with an exceptionally long
> recipient list with the tag in question, and I received it around the
> time I first noticed the bad behavior in sup.  The Cc: field is 6878
> bytes long, containing 281 email addresses.

Weird, because I can call split_on_commas on a string that's that size,
with that many commas, in a few milliseconds. Must be something strange
about that particular string that's causing the worst-case behavior.

I'm going to apply the patch, but with a bigger limit.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2009-11-02 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 17:17 Steven Walter
2009-10-30 21:48 ` William Morgan
2009-10-30 22:14   ` Steven Walter
2009-11-01 14:53     ` William Morgan
     [not found]       ` <e06498070911011203s66ece542mac80378442073369@mail.gmail.com>
2009-11-02 11:53         ` William Morgan [this message]
2009-11-02 12:35           ` William Morgan

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=1257162594-sup-7077@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --cc=stevenrwalter@gmail.com \
    --cc=sup-talk@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