mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-25 04:18:08 +01:00
e0b22c139c
The retries are hardcoded to a small number, and error handling aborts
than propagating errors from notmuch_database_reopen. These are both
somewhat justified by the assumption that most things that can go
wrong in Xapian::Database::reopen are rare and fatal. Here's the brief
discussion with Xapian upstream:
24-02-2017 08:12:57 < bremner> any intuition about how likely
Xapian::Database::reopen is to fail? I'm catching a
DatabaseModifiedError somewhere where handling any further errors is
tricky, and wondering about treating a failed reopen as as "the
impossible happened, stopping"
24-02-2017 16:22:34 < olly> bremner: there should not be much scope for
failure - stuff like out of memory or disk errors, which are probably a
good enough excuse to stop
|
||
|---|---|---|
| .. | ||
| built-with.c | ||
| config.cc | ||
| database-private.h | ||
| database.cc | ||
| directory.cc | ||
| filenames.c | ||
| gen-version-script.sh | ||
| index.cc | ||
| Makefile | ||
| Makefile.local | ||
| message-file.c | ||
| message-private.h | ||
| message-property.cc | ||
| message.cc | ||
| messages.c | ||
| notmuch-private.h | ||
| notmuch.h | ||
| parse-time-vrp.cc | ||
| parse-time-vrp.h | ||
| query-fp.cc | ||
| query-fp.h | ||
| query.cc | ||
| sha1.c | ||
| string-list.c | ||
| string-map.c | ||
| tags.c | ||
| thread.cc | ||