Oliver Tale-Yazdi

Regarding the merge conflicts: its since we renamed `anonymous` to `pure`. I will do a `git merge -X theirs origin/master`.

You can only call the try-runtime bot in Polkadot (Cumulus as well maybe, not sure).

> What we really want is async operations. What kind of operations? For example iterators on `StorageMaps`? So that `StorageMap::iter_keys().map(` would be multi-block operation. Or rather wrapping a whole migration...

Okay so there are a few other cases where multi-block or multi-call aka. *async* operations would be useful: https://github.com/paritytech/substrate/pull/12367#discussion_r991535381 (uses `remove_prefix`) https://github.com/paritytech/substrate/pull/12310 (deletes a `StorageMap` which could produce a too...

> @Lederstrumpf please use `bot merge` next time :) It'll take care of merging the companion automatically. Yea... Now we have to fast-track https://github.com/paritytech/polkadot/pull/6061 since it is blocking the CI...

I think this can be closed as we now have default transactional behaviour for extrinsics.

Okay thanks. Looks like this fixes the weird READ/WRITE numbers discovered in https://github.com/paritytech/polkadot/pull/6173 ([SWC](https://weights.tasty.limo/compare?repo=polkadot&threshold=10&path_pattern=runtime%2F**%2Fsrc%2Fweights%2F**%2F*.rs&method=guess-worst&ignore_errors=true&unit=weight&old=release-v0.9.31&new=coderobe/weights-31)). SWC for [this MR](https://weights.tasty.limo/compare?repo=substrate&threshold=10&path_pattern=frame%2F*%2Fsrc%2Fweights.rs&method=guess-worst&ignore_errors=true&unit=time&old=master&new=shawntabrizi-weights).

> Or should we actually start filling up the proof size weight for each extrinsic? I think we should, https://github.com/paritytech/polkadot-sdk/issues/384. But it could legitimately be that the `base_extrinsic.pov()` is zero,...

bot rebase

CI blocked by https://github.com/paritytech/polkadot/pull/6061