Ruslan Tushov

In commit e11f3ed2292062ee1e1aafe3510802a889ea6f96 I forgot to update silent version (_HackTimer.silent.min.js_) ([issue 13](https://github.com/turuslan/HackTimer/issues/13)) that you used ([package.json](https://github.com/seiyria/Roguathia/commit/ae52477b2f2f69c2031ba51b6238f3abed2f9311#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L59)). So it was not fixed that time. Now it is updated (8e2fef9429ec427a54d8b407a2f1130b5a811098, c06bbc674e3c49d9c250e5890724cbf007c53388).

Seems like `ext_misc_runtime_version_version_1` called by runtime upgrade can randomly fail. E.g. can't instantiate WASM to call `Core_version` because of insufficient resources, depending on total and used RAM. https://kusama.subscan.io/extrinsic/1472960-0?event=1472960-1 Reverting last...

https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/impl/peer_manager_impl.cpp#L294-L323 https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/impl/peer_manager_impl.cpp#L446-L451 https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/impl/peer_manager_impl.cpp#L478-L497

Need to deduplicate/merge `active_peers_` and `peer_states_` https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/peer_manager.hpp#L44-L45 https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/impl/peer_manager_impl.hpp#L48-L49 https://github.com/soramitsu/kagome/blob/a635da383e5e59f6dec407d0eaf7b7a1e6bf2fc9/core/network/impl/peer_manager_impl.hpp#L189-L190

Corrupted messages on `"/ws"` in `YamuxedConnection::doWrite` (seems like `std::function` or boost asio handler didn't move `Bytes`, but copied it)

> Hey, thank you for the pull request. If you want to work on this, please check out [my comment](https://github.com/paritytech/polkadot-sdk/issues/5053#issuecomment-2370371891) and the work for that was already started [here](https://github.com/paritytech/polkadot-sdk/pull/5956). >...

This PR was [backported](https://github.com/turuslan/polkadot-sdk/tree/stable2412-state-sync-resume) and [tested](https://github.com/turuslan/astar/tree/state-sync-resume) on Astar, which had issue with [OOM during parachain state sync](https://github.com/AstarNetwork/Astar/issues/1110). Logs and RAM usage was collected, and following plot suggests that modified state...

> Not sure what you are saying here? > take these nodes and stick them directly into the db, we don't need to recalculate Yes > Not sure how this...

Thanks, checked #5956 again. Don't see complete changes yet: - `StateImporter` is not used yet. - `import_state` still accepts `Storage` (key-value). Your review comment suggests to forward proof `PrefixedMemoryDB` to...

> why not merge all? why order is important? [Example](https://github.com/paritytech/polkadot-sdk/pull/9247#issuecomment-3284006245) shows that merging whole proof may break database. In that example there are three nodes: root node with hash `root1`,...