Bad state if connecting to a cabal with --db and then --key /wo peers
cblgh opened this issue · comments
05:46:38 <noffle> cblgh: there's a bug where if you run 'cabal --db foo' and then
'cabal --key dat://...' from that 1st cabal, if you didn't sync it first /w others, you can
end up in a bad state
not relevant anymore