cosmos-omnibus
cosmos-omnibus copied to clipboard
ovrclk
Usually there's one PR per project/chain and all the chains are tested while the PR is open. This PR aims to detect the project/chain that has been changed and just...
> image: `ghcr.io/akash-network/cosmos-omnibus:v0.4.0-generic` `cosmos-omnibus` should not start if it fails to obtain (download/extract) the snapshot It should fail to start when it is unable to download or extract the snapshot...
Hi, after deploying node via [cloudmos](https://deploy.cloudmos.io/) it fails to to start with following error: ``` panic: runtime error: invalid memory address or nil pointer dereference [node]: [signal SIGSEGV: segmentation violation...
As per Polkachu: > It is better than the old implementation. It only provides up to 5 random live peers plus a polkachu internal one. It is less likely to...
cosmovisor 1.5.0 changelog https://github.com/cosmos/cosmos-sdk/blob/tools/cosmovisor/v1.5.0/tools/cosmovisor/CHANGELOG.md I think adding a default `DAEMON_SHUTDOWN_GRACE=15s` variable would not hurt. > `DAEMON_SHUTDOWN_GRACE` (optional, default none), if set, send interrupt to binary and wait the specified time...
A shell script is running the binary, when the container receives SIGTERM (say on Pod termination or `docker stop / kill` with the default `SIGTERM`, or Ctrl+C - `SIGINT`) the...
Set `SNAPSHOT_DATA_PATH=data` always by default when `SNAPSHOT_DATA_PATH` is not set. Otherwise the node will just either start syncing / or get stuck (due to version incompatibility) from/at the `height=1`: `12:50PM...
some snapshots have `data` and `wasm` directories, I think they should get automatically detected before the extraction. they are currently getting set via these variables: ``` - SNAPSHOT_WASM_PATH=wasm - SNAPSHOT_DATA_PATH=data...