From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id E37326DE0C64 for ; Sat, 12 Nov 2016 13:36:48 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.006 X-Spam-Level: X-Spam-Status: No, score=-0.006 tagged_above=-999 required=5 tests=[AWL=0.005, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g44UMm6cIkjG for ; Sat, 12 Nov 2016 13:36:48 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 4346D6DE0C5F for ; Sat, 12 Nov 2016 13:36:48 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1c5fyJ-0003Jr-AM; Sat, 12 Nov 2016 16:36:23 -0500 Received: (nullmailer pid 17313 invoked by uid 1000); Sat, 12 Nov 2016 21:36:41 -0000 From: David Bremner To: Brian Sniffen Cc: Paul Wise , Jani Nikula , notmuch@notmuchmail.org Subject: Re: [PATCH] cli: consider files vanishing during notmuch new non-fatal In-Reply-To: References: <1478312104.1979.8.camel@debian.org> <1478350621-17137-1-git-send-email-jani@nikula.org> <1478352176.17295.5.camel@debian.org> <87k2c8u2q1.fsf@tethera.net> <60C96E28-48D2-4307-A991-A68469733955@evenmere.org> <87h97cu1am.fsf@tethera.net> Date: Sat, 12 Nov 2016 17:36:41 -0400 Message-ID: <878tsotm6u.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2016 21:36:49 -0000 Brian Sniffen writes: > That's hard, given dovecot pointed at the same maildir: it quickly > moves files from new to cur. That makes notmuch insert pretty useless, > and I rely on notmuch new to approach correctness. I don't think this discussion is related to notmuch insert at all. If you have found a race condition (or some other concurrency issue) in notmuch-insert please report that seperately. > > But maybe I misunderstand: is the idea that it will return an error >but keep processing? Or stop on that error? The whole discussion started because under certain circumstances it will stop processing. The proposed patch makes it continue processing, but report an error at the end.