Andrew Plaza

yeah we're just waiting on a release of xtra. Not really high on priorities since it won't change the functionality of archive in any way other than improve the code...

after running archive and logging some extra data, most of the blocks causing this issue are from the problematic v30 polkadot runtime, or it's possible we are just going OOM....

Yeah the docs can be confusing here, I think > This example: https://github.com/paritytech/substrate-archive/wiki/1).-Requirements#example-setting-up-the-database seems to be the right place to provide steps on how to do this. Perhaps we could...

@xcaptain There's an actor to decode extrinsics and it works, with some caveats: - there may be discrepencies between the formats of newer, scale-info-produced JSON and `legacy-desubj` produced JSON (in...

blocked on https://github.com/paritytech/desub/pull/86

This looks good (if it's decided nix is ok to use for archive), I can post my old nix config too if that's of interest. I think [Oxalica](https://github.com/oxalica/rust-overlay) is definitely...

Sure! That would be awesome. Creating the tables/relationships shouldn't be necessary though, on first run if the expected database exists, substrate-archive will handle the database migrations. So, just instantiation of...

I believe this will be solved by only executing finalized blocks; rel #229 Thanks for the report! this happens when archive is trying to execute blocks that have not yet...

https://github.com/insipx/desub and https://github.com/insipx/cargo-git-edit could export all runtime types for all polkadot versions (at first only from 0.7, Kusama CC3) and decode them, leaving substrate-archive only to import the resulting JSON...

Desub is in a state where it will be integrated with substrate-archive