Jack Zampolin
Jack Zampolin
So not really sure quite where to start with this. I'm a maintainer on both of the helm charts involved here so I'm a bit perplexed not being able to...
The provider daemon should be able to introspect into a kube cluster and see if the required CRDs and other resources.
**Describe the bug** Sometimes my tests stall around exit and then the test runner panics with a timeout. This results in the docker daemon needing to be restarted. **To Reproduce**...
panic: runtime error: index out of range [0] with length 0 goroutine 1 [running]: github.com/peggyjv/gravity-bridge/module/x/gravity/client/cli.CmdUnbatchedSendToEthereums.func1(0xc0011c8500, 0x328ed98, 0x0, 0x0, 0x0, 0x0) /home/runner/go/pkg/mod/github.com/peggyjv/gravity-bridge/[email protected]/x/gravity/client/cli/query.go:667 +0x3f4 github.com/spf13/cobra.(*Command).execute(0xc0011c8500, 0x328ed98, 0x0, 0x0, 0xc0011c8500, 0x328ed98) /home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:856 +0x472...
In addition to logging, metrics based monitoring and dashboards should also be added.
It appears that eth signatures for batches aren't being pruned at the same time batches are being pruned: ``` $ sommelier q gravity batch-tx-ethereum-signatures 1 0xa670d7237398238de01267472c6f13e5b8010fd1 signatures: - batch_nonce: "1"...
This program should: - [ ] go through each chain.json and ensure that the correct mainnet version is there - [ ] ensure that seeds and rpc endpoints are active...