<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/bindings/python-cffi, branch debian/0.38_rc2-1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.38_rc2-1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.38_rc2-1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-08-16T07:29:39Z</updated>
<entry>
<title>test: increase cffi timeout</title>
<updated>2022-08-16T07:29:39Z</updated>
<author>
<name>Michael J Gruber</name>
<email>git@grubix.eu</email>
</author>
<published>2022-08-14T15:22:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=760431c0a3216605d3690e963bb8fa3e3c8788cb'/>
<id>urn:sha1:760431c0a3216605d3690e963bb8fa3e3c8788cb</id>
<content type='text'>
By default, the test suite uses 2min for other tests and 5s for cffi
tests. Sporadically, this leads to test failures caused by the timeout
on slower or loaded test infrastructure (as seen on ppc64le in Fedora's
infrastructure during branch time).

Increase the cffi timeout to the same 2m=120s.

Signed-off-by: Michael J Gruber &lt;git@grubix.eu&gt;
</content>
</entry>
<entry>
<title>bindings/python-cffi: fix docstring</title>
<updated>2022-07-05T10:34:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-03T20:26:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=db44af75ad5a79b3fd5ecad93fe95195ef175ebd'/>
<id>urn:sha1:db44af75ad5a79b3fd5ecad93fe95195ef175ebd</id>
<content type='text'>
the method Database.get_message does exist any more (if it ever
did). This makes the docstring unhelpful as an example.
</content>
</entry>
<entry>
<title>lib: add NOTMUCH_STATUS_CLOSED_DATABASE, use in _n_d_ensure_writable</title>
<updated>2022-06-25T19:06:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-05-25T10:51:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3f27cce71f9f154cb0c2134c32d41c31eb62a239'/>
<id>urn:sha1:3f27cce71f9f154cb0c2134c32d41c31eb62a239</id>
<content type='text'>
In order for a database to actually be writeable, it must be the case that it
is open, not just the correct type of Xapian object. By explicitely
checking, we are able to provide better error reporting, in particular
for the previously broken test in T566-lib-message.
</content>
</entry>
<entry>
<title>python-cffi: use config_pairs API in ConfigIterator</title>
<updated>2022-02-17T01:57:22Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-02-09T12:28:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9ddd13f75827f4972872c8766320c7cb80b1819b'/>
<id>urn:sha1:9ddd13f75827f4972872c8766320c7cb80b1819b</id>
<content type='text'>
This returns all of the config keys with non-empty values, not just
those that happen to be stored in the database.
</content>
</entry>
<entry>
<title>lib/open: no default mail root in split configurations</title>
<updated>2022-01-15T19:59:39Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-12-25T13:33:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fad2e7540bf9309bfb335650ded753e9ed085eff'/>
<id>urn:sha1:fad2e7540bf9309bfb335650ded753e9ed085eff</id>
<content type='text'>
If we know the configuration is split, but there is no mail root
defined, this indicates a (lack of) configuration error. Currently
this can only arise in XDG configurations.
</content>
</entry>
<entry>
<title>Merge tag '0.34.3'</title>
<updated>2022-01-09T23:34:58Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-09T23:34:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=63d3b2b5cf8702b5fecea77392ce46f8a8249175'/>
<id>urn:sha1:63d3b2b5cf8702b5fecea77392ce46f8a8249175</id>
<content type='text'>
notmuch 0.34.3 release
</content>
</entry>
<entry>
<title>version: bump to 0.34.3</title>
<updated>2022-01-09T19:35:12Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-09T19:35:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a226b7a29b8977003081d96850a1f9e2b9a962b9'/>
<id>urn:sha1:a226b7a29b8977003081d96850a1f9e2b9a962b9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>bindings/python-cffi: search for config by default</title>
<updated>2022-01-09T19:16:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-08T21:21:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8b737af28bc377db3e661a5744f3b7479b7ce485'/>
<id>urn:sha1:8b737af28bc377db3e661a5744f3b7479b7ce485</id>
<content type='text'>
The previous (pre-0.34.2) constructor searched for a config file but
only if the database path was not specified, and only to retrieve
database.path. Neither of the available options (CONFIG.SEARCH or
CONFIG.NONE) matches this semantics exactly, but CONFIG.SEARCH causes
less breakage for people who relied on the old behaviour to set their
database.path [1]. Since it also seems like the friendlier option in
the long run, this commit switches to CONFIG.SEARCH as default.

This requires a certain amount of updating the pytest tests, but most
users will actually have a config file, unlike the test environment.

[1]: id:87fsqijx7u.fsf@metapensiero.it
</content>
</entry>
<entry>
<title>Merge branch 'release'</title>
<updated>2022-01-09T13:20:56Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-09T13:20:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=22e04ed01acc115b7fb25b60231014f585f11c4a'/>
<id>urn:sha1:22e04ed01acc115b7fb25b60231014f585f11c4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>python-cffi: returned OwnedMessage objects from Message.replies</title>
<updated>2022-01-08T20:29:41Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-01-08T14:03:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9e7ea628e6bddbd7345d053a3daf14af74896cc2'/>
<id>urn:sha1:9e7ea628e6bddbd7345d053a3daf14af74896cc2</id>
<content type='text'>
If we return regular Message objects, python will try to destroy them,
and the underlying notmuch object, causing e.g. the crash [1].

[1]: id:87sfu6utxg.fsf@tethera.net
</content>
</entry>
</feed>
