Quentin McGaw

## Changes - [x] Use generated mockery constructors for mockery mocks to ensure assertions are done in the test - [x] Fix bugs caused by the now-fixed mock assertions -...

For newer runtimes, the runtime version can now be obtained from the WASM custom sections from the wasm code, and there is no longer a need to instantiate the full...

feat(wasmer): get and cache state version in instance context

1

## Changes Note this caches the state version for usages in several import functions (see #2664) - [x] Codec support for Core_version and state_version - [x] Cache state version in...

## Changes Devnet tests were not run previously. ## Tests ## Issues ## Primary Reviewer @timwu20

Trie code uses `scale.Marshal` in a few places and then copies the resulting scale encoded byte slice to another io.Writer (usually a bytes buffer). We could save those copying operations...

chore(lib/grandpa): `lib/grandpa/models` package

7

## Changes - Dumb dumb moving of files from `lib/grandpa` to `lib/grandpa/models` - Minimal diffs, only affects `lib/grandpa` Why: because adding tests in `lib/grandpa` drove me mad having to fiddle...

chore(lib/trie): split fuzz testing of the trie

1

## Changes - Change trie put/get fuzz test to create a new trie per fuzz run, instead of using the same trie (to avoid OOM) - Add unit test to...

chore(ci): add skip workflows to use trigger paths

1

## Changes See https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks This adds 'skip' workflows such that required workflows are still satisfied when no trigger paths for the actual workflow is modified. ## Tests CI passing ##...

fix(trie): use direct Merkle value for database keys

1

## Changes The problem is as follows in this example. For a node `A` encoding to `{1, 2}`, its database key is `{0, 0, 0, ..., 1, 2}`. Another node...

## Task summary Prometheus metric `gossamer_network_node_latency_ms` is always 0, this is likely a bug. We should investigate and fix it at some point.