From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] More about those lost messages
Date: Wed, 08 Apr 2009 15:34:06 -0700 [thread overview]
Message-ID: <1239229590-sup-7235@entry> (raw)
In-Reply-To: <a412e2a70904081032x3438abedw3a23d87973f56d35@mail.gmail.com>
Reformatted excerpts from Mark Alexander's message of 2009-04-08:
> This has happened twice that I've noticed, and in both cases the
> message that got lost was part of a thread in which I was
> participating, and was in the inbox.
Just to confirm: you saw the message in Sup, you quit Sup, and when you
started Sup again, the message wasn't there?
The next time this happens, would you mind trying this? Before running
sup-sync --all, find the message id of the missing message (i.e. from
the mbox file), and run:
devel/console.sh # start the debug console
Index.index.search("message_id:XXX").total_hits # from within the console
where XXX is the message id, without the angle brackets. E.g.
Index.index.search("message_id:a412e2a70904081032x3438abedw3a23d87973f56d35 at mail.gmail.com")
This will tell us whether it's in the index or not, without anything
of Sup's curses interface getting in the way.
If it is in the index (the total_hits is > 0), then try finding the
labels:
docid = Index.index.search("message_id:XXX").hits.first.doc
Index.build_message(docid).labels
> This is just idle, uninformed speculation, but maybe some records that
> were in the in-memory index didn't get written to disk when sup
> exited? Would neglecting to use the '$' command do this?
Sup saves all state when you quit. That's why I'm wondering whether the
messages actually are in the index, or somehow are just hidden from the
curses interface.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-04-08 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 17:32 Mark Alexander
2009-04-08 22:34 ` William Morgan [this message]
2009-04-09 15:36 ` Mark Alexander
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=1239229590-sup-7235@entry \
--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