Closed dimalinux closed 1 year ago
Patch coverage: 84.61
% and project coverage change: +0.89
:tada:
Comparison is base (
0f1865c
) 58.68% compared to head (6ffc244
) 59.57%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
In https://github.com/AthanorLabs/atomic-swap/pull/480, we upgraded
github.com/ChainSafe/chaindb
from the non-released commit hashf900218c88f8
above releasev0.1.4
of to a release that Chainsafe made 2 weeks ago tagged v0.1.5. The release tag is only changing the patch-level, so it should have been backwards compatible, but, sadly, it is not.The
v0.1.5
chaindb release moves to Badger v4.1.0, whose primary purpose is to fix 6 CVE's.Attempting to run
swapd
with an existing database already in place gives this error:This PR gives the database directory a new, more specific, name, to allow startup. That's probably good enough for most people, but we can give the link to that error message in the release notes for anyone that wants to salvage their swap history.
Feel free to suggest alternate ideas, this is just what I came up with.