61ea15eb39
Merge branch 'main' into valere/msc_2399
2023-03-15 19:31:04 +01:00
283137f190
Introduce RoomSettings
2023-03-14 10:27:11 +00:00
7e7c91699f
Generic key-value API
2023-03-14 10:27:11 +00:00
b4b111f91f
Store encryption settings
2023-03-14 10:27:11 +00:00
9733d9842a
Merge branch 'main' into valere/msc_2399
2023-03-09 17:04:21 +01:00
68f8ed5a92
Add futures-util as a workspace dependency
...
… and always activate its `alloc` feature.
Fixes building matrix-sdk without the e2e-encryption feature.
2023-03-08 15:03:20 +01:00
0ec3aca727
refactor(withheld) store withheld as ShareInfo
...
and store no_olm sent in device
2023-03-07 18:46:52 +01:00
6cc31a0e13
fix clippy
2023-02-24 17:15:51 +01:00
6b948711b9
feat(withheld) Integration tests
2023-02-23 17:47:57 +01:00
e56d380f65
fix store after rebase
2023-02-22 14:28:20 +01:00
3dbad4229a
feat(withheld): sql store support
2023-02-21 15:05:14 +01:00
0154cccd4b
feat(withheld) Remember no_olm and implement in memory store
2023-02-21 15:03:04 +01:00
3a516a5fce
refactor(sqlite): Use internal Error in CryptoStore impl
2023-02-13 12:05:04 +01:00
c6f0e47077
refactor(crypto)!: Add an error type to the CryptoStore trait
...
This makes it easier to implement it. However, using a different error
type than CryptoStoreError is a non-trivial change, so left for the
coming commits for all stores except the memory store.
2023-02-13 12:05:04 +01:00
e430f65ce8
ci: Exclude Debug implementations from coverage reports
...
We don't really want to check for exact representations, and otherwise
they are really just invoked in tests that fail.
2023-02-10 13:46:00 +01:00
e25061f8cb
refactor(crypto)!: Unwrap unused Result
2023-02-08 16:04:29 +01:00
345f4f39f4
refactor(sqlite): Make Error more precise / useful
2023-02-08 15:44:17 +01:00
e12b9e3027
refactor(sqlite): Encode olm hashes with rmp instead of serde_json
...
… like everything else in the sqlite crypto store.
2023-02-08 15:44:17 +01:00
a22529344a
refactor(sqlite): Inline inherent methods that duplicate trait methods
2023-02-08 15:44:17 +01:00
64b7c4eb59
refactor(sqlite): Make OpenStoreError more precise / useful
2023-02-08 15:44:17 +01:00
1988d1e9a3
refactor(sqlite): Move sqlite extension traits to utils module
2023-02-08 15:44:17 +01:00
efc2397267
refactor(sqlite): Always use rusqlite::Error for sqlite extension traits
2023-02-08 15:44:17 +01:00
ecb521205f
refactor(sqlite): Move error types into new error module
2023-02-08 15:44:17 +01:00
7db40746bb
refactor(sqlite): Start cleaning up cfg attributes
2023-02-08 15:44:17 +01:00
b436918cb3
fix(sqlite): Fix Debug output for SqliteCryptoStore
2023-02-06 17:08:21 +01:00
b20424b8b5
chore(sqlite): Undo weird formatting of TOML file
2023-02-06 17:08:21 +01:00
fc8cd2e7e5
chore(deps): bump tokio from 1.24.1 to 1.24.2
...
Bumps [tokio](https://github.com/tokio-rs/tokio ) from 1.24.1 to 1.24.2.
- [Release notes](https://github.com/tokio-rs/tokio/releases )
- [Commits](https://github.com/tokio-rs/tokio/commits )
---
updated-dependencies:
- dependency-name: tokio
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com >
2023-02-04 08:27:50 +01:00
e9cef35f99
Add matrix-sdk-sqlite with a CryptoStore implementation
...
Note about "Write-Ahead Log" (WAL) mode: The SQLite WAL mode has a
bunch of advantages that are quite nice to have:
1. WAL is significantly faster in most scenarios.
2. WAL provides more concurrency as readers do not block writers and a
writer does not block readers. Reading and writing can proceed
concurrently.
3. Disk I/O operations tends to be more sequential using WAL.
4. WAL uses many fewer fsync() operations and is thus less vulnerable
to problems on systems where the fsync() system call is broken.
The downsides of WAL mode don't really affect us. So let's turn it on.
More info: https://www.sqlite.org/wal.html
Co-authored-by: Jonas Platte <jplatte@matrix.org >
Co-authored-by: Damir Jelić <poljar@termina.org.uk >
2023-02-01 15:06:59 +01:00
Damir Jelić