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:[email protected]")
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 <[email protected]>
_______________________________________________
sup-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/sup-talk
