[bisq-network/bisq] SPV file is deleted after SPV resync (#5335)

[jmacxx]

#5280 was implemented to prevent the write of database files at shutdown if the app was never started fully, thus preventing a scenario when two simultaneous instances of Bisq overwrote all the database files.

A side effect is seen here when SPV resync is done, the preference flag `resyncSpvRequested` is not able to be cleared back to false on completion of the resync.  It says `PersistenceManager: Application has not completed start up yet so we do not flush data to disk` in the log.  The resync is started every time because the flag stays set.

I will submit a PR to use a semaphore file instead of preferences for controlling when an SPV resync is to be performed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/5335#issuecomment-810732663
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210330/360e148f/attachment.htm>