unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@grubix.eu>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] test: change database from within pre-new hook
Date: Wed, 12 May 2021 09:23:15 +0200	[thread overview]
Message-ID: <162080419530.6226.1085165083385413134.git@grubix.eu> (raw)
In-Reply-To: <87fsyshpc6.fsf@tethera.net>

David Bremner venit, vidit, dixit 2021-05-12 00:34:33:
> Michael J Gruber <git@grubix.eu> writes:
> 
> > Due to the change in the config system, notmuch keeps a notmuch database
> > open when it would not do so before. Consequently, it can miss changes
> > to the database which are done from a hook (while notmuch holds the
> > databse in read only mode). When notmuch itself writes to the database
> > after that it uses wrong assumptions about the last used doc id etc.
> >
> > Demonstrate this by triggering an assertion. (This new test succeeds
> > with notmuch 0.31.4.)
> >
> > Signed-off-by: Michael J Gruber <git@grubix.eu>
> > ---
> >  test/T400-hooks.sh | 21 +++++++++++++++++++++
> >  1 file changed, 21 insertions(+)
> 
> > +    notmuch search '*' > change.expected
> 
> That line looks like leftover debugging to me, so I deleted
> it. Otherwise it works fine, thanks for tracking down the bug and
> providing a test.

Thanks for the fix! I didn't put it in the commit message (because
that commit might go before for your patch), but the test succeeds with
your fix.

Sorry for the debug line - typical case of re-editing without
re-format-patching...

I was wondering if it's worthwhile to test also:
- that the change from pre hook is persistent (test for that msg)
- test the same for post (even though the db is closed before)

Cheers
Michael

  reply	other threads:[~2021-05-12  7:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05  7:51 Possible threading issues in nm 0.32 Michael J Gruber
2021-05-05 12:29 ` David Bremner
2021-05-08 15:45   ` Michael J Gruber
2021-05-11 14:04     ` Alexander Adolf
2021-05-11 14:32       ` Alexander Adolf
2021-05-11 15:41         ` Michael J Gruber
2021-05-11 16:56           ` Michael J Gruber
2021-05-11 17:39             ` David Bremner
2021-05-11 17:42             ` [PATCH] lib/notmuch_database_reopen: reload some database metada David Bremner
2021-05-11 17:47               ` David Bremner
2021-05-11 20:17                 ` Michael J Gruber
2021-05-11 20:48                   ` [PATCH] test: change database from within pre-new hook Michael J Gruber
2021-05-11 22:34                     ` David Bremner
2021-05-12  7:23                       ` Michael J Gruber [this message]
2021-05-12 11:47                         ` David Bremner
2021-05-12 12:07                 ` [PATCH] lib/notmuch_database_reopen: reload some database metada David Bremner
2021-05-12 13:30                   ` Michael J Gruber
2021-05-16 11:11                     ` David Bremner

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162080419530.6226.1085165083385413134.git@grubix.eu \
    --to=git@grubix.eu \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).