Database file got corrupted when running parity bridge about poa-bridge HOT 12 OPEN

Moved from omni/bridge-ui#26, which was the wrong repository.

from poa-bridge.

@snd It's probable that I had an extra process running - perhaps it didn't quit correctly on a previous run. Having restarted my machine cleanly, it works correctly now.

But even so, as you said on the other thread, it shouldn't be corrupting the file, regardless.

from poa-bridge.

I take that back. It's still doing it.

I'm using the current master of both parity-bridge (commit e885fdf) and bridge-ui (commit 4aefece)

from poa-bridge.

could you try https://github.com/paritytech/parity-bridge/ to see whether your problem occurs there as well?

from poa-bridge.

Removing the comments in the Config.toml appears to have fixed it.

from poa-bridge.

strange

from poa-bridge.

Same problem here. +1

from poa-bridge.

@yrashk any ideas why?

from poa-bridge.

Also deleting config.toml comments problem disapeared.

from poa-bridge.

@maxidev could you provide more details on the exact project, branch and commit you are using to build the bridge. What steps to reproduce the issue are?

from poa-bridge.

@akolotov to have the bridge working I had to checkout to latest commit from Apr 11 (commit da91da9)
OS: Ubuntu server 16.04
Parity: 1.9.5 Stable
cargo --version
cargo 0.26.0 (41480f5cc 2018-02-26)

from poa-bridge.

@maxidev have you tried any recent version of the bridge?

from poa-bridge.