Kirill Ivanov

Also I wanted to implement `WithPostDispatchInfo` for `DispatchErrorWithPostInfo` to allow builder pattern for the latter (`e.with_pays_fee(Pays::No).with_weight(1234)`). However, that `impl` conflicted with existing `` one ("upstream crates may add a new...

Not sure why the CI doesn't pass with (lack of feature in `sp-keystore`) error. I didn't touch any features 🤔

Seems very related: I get "list index out of range" when there are no elements to tabulate and `maxcolwidths` is set (e.g. `tabulate([],maxcolwidths=[2])`): ``` File ....venv/lib/python3.12/site-packages/tabulate/__init__.py:2054, in tabulate(tabular_data, headers, tablefmt,...

@sevenzing should we close it as completed or something remains to be done?

We are removing support for `.toml` config in the next release, so this issue is now resolved 🙃 🙃

> Total verified contracts affected as well   @yvaskov seems to be in sync, isn't it?

We discussed the problem and possible solutions, so I'll summarize it here. There are 2 main ways to solve the problem (and 1 kinda funny): 1. Calculate total contracts independently...

btw about consistency of calculation methods: There are two methods: via transaction lists and via `addresses`. I ran queries to check differences between results of them (on optimism sepolia; earlier...

from this it might be viable to leave the calculation with `addresses` even after fixing chart `new_contracts`.

seems to work well in staging blockscout api:  stats api:  will close once the next release is shipped & it's confirmed that the problem dissapeared