On Sat, Dec 15, 2012 at 7:18 AM, Austin Clements amdra...@mit.edu wrote:
need to at least os.fsync before the os.link.
Fixed, thanks for the suggestion.
http://git.zx2c4.com/gmail-notmuch/commit/?id=3f9646058bfd91d7d0e2eda035521f97de92eabc
___
Quoth Jason A. Donenfeld on Dec 13 at 3:32 pm:
On Wed, Dec 12, 2012 at 9:49 PM, Austin Clements amdra...@mit.edu wrote:
There should be no way to corrupt the database at this level through
the Xapian API, which means nothing libnotmuch can do (much less users
of libnotmuch) should be able
On Wed, Dec 12, 2012 at 10:26 PM, David Bremner da...@tethera.net wrote:
One thing that Olly Betts mentioned is that there is a recently fixed
bug in xapian with respect to multiple threads in the same process
The script's actually single threaded.
Quoting Jason A. Donenfeld (2012-12-13 14:32:53)
On Wed, Dec 12, 2012 at 9:49 PM, Austin Clements amdra...@mit.edu wrote:
There should be no way to corrupt the database at this level through
the Xapian API, which means nothing libnotmuch can do (much less users
of libnotmuch) should be able
On Tue, Dec 11, 2012 at 7:26 PM, Patrick Totzke patricktot...@gmail.com wrote:
OK, i assumed i'd not have to download all messages because i already have
them
on disk -- synced via offlineimap. but then i remembered that OI stores uses
its own naming scheme for the files in a maildir. so
Quoth Jason A. Donenfeld on Dec 12 at 7:35 pm:
On Tue, Dec 11, 2012 at 7:26 PM, Patrick Totzke patricktot...@gmail.com
wrote:
i am kind of reluctant to reproduce this again (on my work-desktop).
It'd really be a huge help if you could backup and try...
All i did was start your script,
Austin Clements amdra...@mit.edu writes:
There should be no way to corrupt the database at this level through
the Xapian API, which means nothing libnotmuch can do (much less users
of libnotmuch) should be able to corrupt the database. If you can
reproduce the problem, it's probably a
Quoting Jason A. Donenfeld (2012-12-11 13:47:32)
On Tue, Dec 11, 2012 at 11:04 AM, Patrick Totzke
patricktot...@gmail.com wrote:
I ended up killing the process after i saw that ETA was 3h.
Gmail's bottleneck. Very unfortunate. Leave it going over night.
OK, i assumed i'd not have to
