poanetwork
/
poa-bridge
mirror of https://github.com/poanetwork/poa-bridge.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
poa-bridge/cli/Cargo.toml

25 lines
408 B
TOML
Raw Normal View History

repo overhaul, separated binary from library, closes #10, added tests crate
2017-08-24 15:36:13 -07:00
[package]
name = "bridge-cli"
Bump version to 0.3.0
2018-05-31 13:45:34 -07:00
version = "0.3.0"
repo overhaul, separated binary from library, closes #10, added tests crate
2017-08-24 15:36:13 -07:00
[[bin]]
name = "bridge"
path = "src/main.rs"
[dependencies]
bridge = { path = "../bridge" }
serde = "1.0"
serde_derive = "1.0"
tokio-core = "0.1.8"
docopt = "0.8.1"
log = "0.3"
cli/Cargo.toml: bump `env_logger` to `0.4`
2018-02-15 04:13:59 -08:00
env_logger = "0.4"
bridge writes to backing database
2017-08-28 07:48:01 -07:00
futures = "0.1.14"
Problem: bridge crashes with insufficient balance Currently there are two possible situations related to low balance on the account which is used for bridge operations: 1. The account which is used to sign transactions to be addressed by ForeignBridge contract has low balance. So, the bridge is not able to do deposit_relay and withdraw_confirm. 2. The account which is used to sign transactions to be addressed by HomeBridge contract has low balance. So, the bridge is not able to do withdraw_relay. In both cases bridges hangs silently at the moment of sending transactions and does not proceed with further actions even the operation is intended to be performed in opposite direction (e.g. the bridge hangs at the moment to perform withdraw_relay, so deposit_relay cannot be performed either). Solution: make bridge track its balance and hande insufficient Bridge will crash with ERR_INSUFFICIENT_FUNDS (code 4) so that supervisor can decide what should happen next. It will also log the condition. P.S.Make sure to run the tests with `--test-threads=1` to avoid other test conflicting with this one. A better solution to this issue must be devised later, however.
2018-04-03 23:42:16 -07:00
jsonrpc-core = "8.0"
Problem: intentional bridge shutdowns It is impossible to tell whether the bridge is being shut down intentionally or because of an error. This is particularly important for supervising the process, both in development and production. Solution: handle SIGINT and SIGTERM as a special case and designate a separate status code (3) for intentional shutdowns. Also, include an example supervisor for development mode (examples/suprevisor). Simply prepend it before the invocation of bridge to supervise it.
2018-03-15 07:10:53 -07:00
ctrlc = { version = "3.1", features = ["termination"] }
Problem: hard to check which version the bridge is Solution: introduce `bridge -v|--version` flag to print the version The version is built off `git describe`, however, as a backup, if `git describe` fails (stripped .git, etc.), this will fall back to whatever is specified in Cargo.toml Fixes #87
2018-05-31 14:05:19 -07:00
version = "3"
Problem: bridge should not deploy its contracts anymore Bridge's contracts are now developed in a separate repository and have their own deployment procedure: https://github.com/poanetwork/poa-parity-bridge-contracts However, our integration tests are not yet updated to use this deployment procedure. Solution: disable deployment compile-time by default and only use it in integration tests as a stopgap measure until the new deployment procedure (or any other viable alternative) has been used.
2018-05-01 09:43:34 -07:00
[features]
default = []
deploy = ["bridge/deploy"]