Christian Decker f34787d065 backup: Rely solely on backup.lock and do not cache writes ...

Caching writes was causing us some issues if the startup of
`lightningd` didn't complete, i.e., the writes would happen on the
live DB, but we'd forget about them. Since we have the backup.lock
file in same directory as the plugin is running in, we no longer have
to defer the writes. This hugely simplifies our logic.

Fixes #155

Changelog-Fixed: backup: The plugin doesn't lose sync anymore if the startup is interrupted

2020-11-25 19:26:44 +01:00

..

backup-cli

backup: Refuse to create a new FileBakend if the backing file exists

2020-04-12 19:35:21 +02:00

backup.py

backup: Rely solely on backup.lock and do not cache writes

2020-11-25 19:26:44 +01:00

requirements.txt

noise: Add missing dependency on psutil>=5

2020-10-21 16:13:29 +02:00

test_backup.py

backup: Rely solely on backup.lock and do not cache writes

2020-11-25 19:26:44 +01:00