notmuch, branch debian/0.30_rc2-1thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.30_rc2-12020-06-16T11:42:07Zdebian: changelog stanza for 0.30~rc2-12020-06-16T11:42:07ZDavid Bremnerdavid@tethera.net2020-06-16T11:32:51Zurn:sha1:af51e67127e5817e3795973da9c5e2148b7fdeecversion: update to 0.30~rc22020-06-16T11:29:39ZDavid Bremnerdavid@tethera.net2020-06-16T11:29:39Zurn:sha1:cda6e4d1046641871413710f3786c43697bd6d19debian/copyright: update to match AUTHORS2020-06-16T11:28:08ZDavid Bremnerdavid@tethera.net2020-06-16T11:28:08Zurn:sha1:6b3b0ae18602252d333dee77149363b5ffc67a13update AUTHORS2020-06-16T11:26:55ZDavid Bremnerdavid@tethera.net2020-06-16T11:26:55Zurn:sha1:5e163465935f42ed5d4c2af13cf8fc535ae5b729
Yay, we gained a new author, thanks Anton.
Support aborting the atomic context2020-06-16T11:17:39ZFloris Bruynoogheflub@devork.be2020-06-14T15:23:19Zurn:sha1:776a54a0e437651abd69a03b9f7d591ea1f992cb
Since it is possible to use an atomic context to abort a number of
changes support this usage. Because the only way to actually abort
the transaction is to close the database this must also do so.
Amended by db: Note the limitation requiring close is a limitation of
the underlying notmuch API, which should be fixed in a future notmuch
release.
Make messages returned by Thread objects owned2020-06-16T11:02:02ZFloris Bruynoogheflub@devork.be2020-06-15T20:58:50Zurn:sha1:2d895a0119b423b117d10e890c9e0eb5d2a9cdf8
This reverses the logic of StandaloneMessage to instead create a
OwnedMessage. Only the Thread class allows retrieving messages more
then once so it can explicitly create such messages.
The added test fails with SIGABRT without the fix for the message
re-use in threads being present.
python/notmuch2: do not destroy messages owned by a query2020-06-16T11:02:02ZAnton Khirnovanton@khirnov.net2020-06-15T20:58:49Zurn:sha1:131757907907380213b32934d9e73cec942ace43
Any messages retrieved from a query - either directly via
search_messages() or indirectly via thread objects - are owned by that
query. Retrieving the same message (i.e. corresponding to the same
message ID / database object) several times will always yield the same
C object.
The caller is allowed to destroy message objects owned by a query before
the query itself - which can save memory for long-lived queries.
However, that message must then never be retrieved again from that
query.
The python-notmuch2 bindings will currently destroy every message object
in Message._destroy(), which will lead to an invalid free if the same
message is then retrieved again. E.g. the following python program leads
to libtalloc abort()ing:
import notmuch2
db = notmuch2.Database(mode = notmuch2.Database.MODE.READ_ONLY)
t = next(db.threads('*'))
msgs = list(zip(t.toplevel(), t.toplevel()))
msgs = list(zip(t.toplevel(), t.toplevel()))
Fix this issue by creating a subclass of Message, which is used for
"standalone" message which have to be freed by the caller. Message class
is then used only for messages descended from a query, which do not need
to be freed by the caller.
python config access: fix style and KeyError bug2020-06-16T00:50:03ZFloris Bruynoogheflub@devork.be2020-06-15T21:55:53Zurn:sha1:1bca41698a03980b701558fb5c481ef0a340460d
This fixes some minor style/pep8 things and adds tests for the new
config support. Also fixes a bug where KeyError was never raised
on a missing key.
python/notmuch2: add bindings for the database config strings2020-06-16T00:50:03ZAnton Khirnovanton@khirnov.net2020-06-15T21:55:52Zurn:sha1:5a58754841f4d3e62d104ad338c8ca2c481dc32eUpdate tox.ini for python3.8 and fix pypy3.62020-06-15T14:25:39ZFloris Bruynoogheflub@devork.be2020-06-14T19:25:46Zurn:sha1:b7e3a347ac71d2d31747259d4b3bfa089fbaa2b1
Python 3.8 has been released for a while now, make sure we keep
supporting it correctly.
PyPy 3.6 wasn not configured correctly.