Juno Yu

also ``` INFO 08/19-16:35:51.147 /subscan/internal/service/substrate.go:170 Block num 7681905 hash 0xf4398cfe61855831b75ece5ce7370d02ef286860254afb5b917ecd84020d0aef [28/1822] ERROR 08/19-16:35:51.167 /subscan/internal/service/substrate.go:229 Create chain block error Error 1406: Data too long for column 'logs' at row 1 ERROR...

seem to be a new feature that only index from last batch of blocks , in that case seem ok to expect creating tables by self , how do that...

seem related to customization of `tag_prefix` , with that somtimes not working as intended , once some commits it would break ``` - name: Get Timestamp Action id: time uses:...

``` Run mathieudutour/[email protected] ##[debug]Found Invalid Tag: [object Object]. ##[debug]Found Invalid Tag: [object Object]. ##[debug]Found Invalid Tag: [object Object]. ##[debug]Found Invalid Tag: [object Object]. ##[debug]Found Invalid Tag: [object Object]. ##[debug]Found Invalid...

looks this is creating some invalid ref , not a tag nor a branch for `release-v0.1.2` in this run , the url `https://github.com/aaaaaa/XXXXXXXX-yyyyyy/compare/v0.1.1...release-v0.1.2` is visitable but it isn't valid in...

same ``` panic: TODO: register swagger in app goroutine 1 [running]: github.com/kava-labs/kava/app.(*App).RegisterAPIRoutes(0x22ff648, 0xc000c68380, {0x1, 0x1, 0x0, {0xc000161660, 0x12}, 0x3e8, 0x1e, 0x0, ...}) /root/kava/app/app.go:790 +0x392 github.com/cosmos/cosmos-sdk/server.startInProcess(_, {{0x0, 0x0, 0x0}, {0x2339950, 0xc0099caa00},...

issues are still there in v1.7.2 although ``` Coreth Fixed memory leak in the estimate gas API. ``` seem issues in other calls too

Seeing similar things on mainnet ``` About to start processing data on the mainnet network for tezos 2022.04.02 04:18:13 [main] INFO TezosIndexer (tech.cryptonomic.conseil.indexer.tezos.TezosIndexer.checkTezosConnection:111) - Successfully made initial connection to Tezos...

it looks that conseil might do some partial insert which makes things fail to run again if a batch fails to finish the workaround i use for making things continue...

I got docker-compose of all those conseil+psql + tezos running for mainnet, most tunings do not help much until i determined to scale up my instance to a 8core 32GB...