Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: John Wyzer <john.wyzer@gmx.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] message missing in source, sup v0.12.1, sup-sync no longer has --changed?
Date: Sun, 13 Feb 2011 09:20:13 +0100	[thread overview]
Message-ID: <1297584795-sup-2477@localhost> (raw)
In-Reply-To: <1297452493-sup-3136@spade.spade-domain>

Excerpts from Jon Austin's message of Fri Feb 11 20:29:28 +0100 2011:
> I think sup-sync -o may fix it.
> 
> (I've been having a strange issue since .12 came out if I send a message and then quit sup, then relaunch, it'll show the first line of the message, ending in '.....' and then show the below error (inside the message), until I sup-sync -o)
> 
> ***********************************************************************
>  An error occurred while loading this message.
> ***********************************************************************
> 
> I even spent several hours yesterday completely rebuilding the xapian index, but still happening...if anyone has a clue what could be causing this, I'd love to hear it :)


Hmm. In lib/sup/index.rb it says:
  ## xapian-compact takes too long, so this is a no-op
  ## until we think of something better
  def optimize
  end

And from what I understand, the -o optime does not do more at the moment.

So the question remain - if messags are missing from one Maildir, is my only option to dump, reindex all and restore?
That would be painful given the number of messages...

-- 
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  parent reply	other threads:[~2011-02-13  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  5:57 John Wyzer
     [not found] ` <1297452493-sup-3136@spade.spade-domain>
2011-02-13  8:20   ` John Wyzer [this message]
2011-02-13 13:59     ` Moritz Wilhelmy
2011-02-13 18:03       ` Rich Lane
2011-02-13 11:27 ` Sascha Silbe

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=1297584795-sup-2477@localhost \
    --to=john.wyzer@gmx.de \
    --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