Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kevin.mark@verizon.net (Kevin Mark)
Subject: [sup-talk] Amazon.com messages can't be added to index
Date: Sun, 14 Oct 2007 01:20:03 -0400	[thread overview]
Message-ID: <20071014052003.GE17985@horacrux> (raw)
In-Reply-To: <b1d95faa0710132032s72d54ea1y1899a90f71b43654@mail.gmail.com>

On Sat, Oct 13, 2007 at 08:32:23PM -0700, jenny w wrote:
> Hi,
> 
> I just installed sup and am quite excited to check it out in action. I
> haven't gotten much further than my first sync (27k messages over
> IMAPS), but I've noticed something that I didn't in the archives
> (relying on Google for searching).
> 
> Messages I've received from Amazon.com seem to consistently bring up
> an exception on line 157 of 188 of index.rb in the 0.1 release. I saw
> in the troubleshooting tips to try the version from svn but I get a
> similar exception. So I just changed "raise" to "puts", under the
> assumption this means that I just won't be able to search old
> Amazon.com messages. Right now I don't know if this is all Amazon.com
> messages or just some of them. After the sync is done I'll see if I
> can reproduce with just one message and try to narrow down what about
> the message is causing the problem.
> 
> Anyway, thought I'd mention it in case someone knows about this
> problem, or in case it helps track down what the problem is (the
> comment above line 188 is 'this hasn't been triggered in a long time.
> TODO: decide whether it's still a problem.')
> 
> Sample error message:
> 
>     just added message .AAA-notification-24668,
> 9630.1162603428 at na-rte-app-5104.iad5.amazon.com but couldn't find it
> in a search

It would be helpful to the list to show a portion of the actual error
message(or all of it if its small) instead of a restatement of it. A
restatement of an error message is rarely adequet to solve an error.

-- 
|  .''`.  == Debian GNU/Linux == |       my web site:           |
| : :' :      The  Universal     |mysite.verizon.net/kevin.mark/|
| `. `'      Operating System    | go to counter.li.org and     |
|   `-    http://www.debian.org/ |    be counted! #238656       |
|  my keyserver: subkeys.pgp.net |     my NPO: cfsg.org         |
|join the new debian-community.org to help Debian!              |
|_______  Unless I ask to be CCd, assume I am subscribed _______|


  reply	other threads:[~2007-10-14  5:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14  3:32 jenny w
2007-10-14  5:20 ` Kevin Mark [this message]
2007-10-14  9:04   ` jenny w
2007-10-14 21:23     ` Christopher Warrington
2007-10-14 22:32       ` jenny w
2007-10-28  3:06         ` William Morgan
2008-02-22 15:46 Luis Villa
2008-02-22 16:25 ` Luis Villa
2008-02-25  5:10   ` William Morgan
2008-02-25 17:08     ` Christopher Warrington
2008-02-25 17:13       ` 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=20071014052003.GE17985@horacrux \
    --to=kevin.mark@verizon.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