RicoToothless
RicoToothless
`tmkms` keeps showing these errors: ``` 2022-08-15T11:23:00.638916Z DEBUG tmkms::session: [come-chain-id@tcp://ooss.ooss:1234] connecting to validator... 2022-08-15T11:23:00.639064Z INFO tmkms::connection::tcp: KMS node ID: ooxxooxx 2022-08-15T11:23:10.911281Z ERROR tmkms::client: [come-chain-id@tcp://ooss.ooss:1234] protocol error: 0: io error 1:...
We are facing a similar issue as well. Our validator is up but it keeps missing blocks after we created a new validator. The strange thing is, it is fine...
face same issue with [bitnami/kong](https://github.com/bitnami/charts/tree/master/bitnami/kong) too Bitnami Kong also use `post-install` to create a job, but not show in events ``` kubectl -n get events --sort-by='{.lastTimestamp}' ``` and thx @andormarkus...
> I believe this was resolved by #786. After upgrading the Helm provider to 2.4, the 'wait' attribute of the `helm_release` is respected during `terraform destroy`. I think is nope....
I face the same issue, too.
maybe write a if statement? ``` if(env.gitlabActionType == 'PUSH') { if (env.gitlabBranch == 'develop') { stage('DoSomething') { sh "..." } } } ``` and if you want to trigger a...
what a champion LOL