mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2026-11-03 06:48:18 +00:00
Adopt published Commonlib 0.2.3 for Journal recovery
This commit is contained in:
1 parent
901c125723
commit
f2d364b736
4 files changed
+14
-11
No files matched your search
+4
-1
@@ -13,9 +13,12 @@ Earlier releases remain available in the 1.0 release history, the 1.0 preview hi
|
||||
## Unreleased
|
||||
|
||||
- Files containing a raw unit separator (`U+001F`) retain their complete contents when received through S3-compatible Object Storage. (#1303)
|
||||
- The Journal receiver preserves the complete Chunk payload, including batches written by earlier versions, without changing the stored format.
|
||||
- The Journal receiver in Commonlib 0.2.3 preserves the complete Chunk payload, including batches written by earlier versions, without changing the stored format.
|
||||
- Updating prevents further truncation during reception but does not repair existing damaged copies. Update every participating client, preserve an intact recovery source, and follow the [recovery procedure](docs/recovery.md#recover-files-truncated-during-object-storage-reception). Rebuild and Fetch leave Hidden File Sync and Customisation Sync disabled until they are deliberately initialised again.
|
||||
|
||||
- Files waiting for encrypted Chunks which arrive after their Metadata receive the decrypted contents once the local database is ready.
|
||||
- Commonlib 0.2.3 restarts the database change feed after initialisation installs the decryption transforms. This corrects delivery of later Chunks; it does not replay earlier events. ([Commonlib #191](https://github.com/vrtmrz/livesync-commonlib/pull/191))
|
||||
|
||||
- The CLI mirror now starts correctly on Windows when the Vault path is omitted and the database directory is also used as the Vault. It checks logical Vault paths using `/` separators, correctly excluding internal database files and nested hidden directories even when the host uses Windows path separators.
|
||||
|
||||
## 1.0.43
|
||||
|
||||
Reference in new issue
Block a user