| Age | Commit message (Collapse) | Author |
|
|
|
|
|
fixes #707
|
|
fixes #534
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixes #923
Co-authored-by: eta <eta@theta.eu.org>
|
|
|
|
* Swedish translations
* Translate OMEMO strings to Swedish
|
|
|
|
"Can't set a target list on a widget until you've called gtk_drag_dest_set() to make the widget into a drag destination"
|
|
|
|
|
|
fixes #886
|
|
|
|
|
|
from stream
If a info request did not receive a response in some stream (e.g. due to network errors), any requests to the same entity in subsequent streams waited indefinitively.
|
|
|
|
|
|
|
|
|
|
Setting PRAGMA synchronous = 0 is really unsafe, and leads to database
corruption (which I've personally experienced). This commit uses
SQLite's Write-Ahead Log (WAL) [1] instead, together with synchronous =
NORMAL. According to [1], this trades off performance for durability
(i.e. it's possible that some transactions may not have committed if the
power gets lost), but still guarantees that the database won't corrupt
itself.
Together, these changes should improve reliability whilst either
improving or having no effect on performance.
[1]: https://www.sqlite.org/wal.html
|
|
|
|
|
|
Fixes #911
|
|
Fixes #909
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
payload
|
|
|
|
fixes #901
|
|
|
|
|
|
fixes #831
|
|
|
|
|
|
|
|
|
|
|