Fix: check auth changes before processing block

[dimartiro]

Changes

• Process block headers and data before importing the block
• Implement vdt for runtime.DigestItem

This changes will fix 2 issues:

• When we have to apply forced changes for the current block right before processing it.
• Decoding header digests in grandpa justifications.

Tests

make test

Issues

closes #4281

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Project coverage is 53.14%. Comparing base (d1ca7aa) to head (18c2431).
Report is 204 commits behind head on development.

Additional details and impacted files

@@               Coverage Diff               @@
##           development    #4336      +/-   ##
===============================================
+ Coverage        50.51%   53.14%   +2.62%     
===============================================
  Files              230      299      +69     
  Lines            29006    38244    +9238     
===============================================
+ Hits             14653    20323    +5670     
- Misses           12856    15988    +3132     
- Partials          1497     1933     +436     

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[haikoschol]

@dimartiro I was too late to check on Grafana how far the node has synced and my local node hasn't gotten to the problematic block yet. But based on your screenshot on the issue and the code changes, I believe that the issue is fixed.

[haikoschol]

The latest deployment stalled at block #1491033. Apart from lots of networking errors, I found this in the logs:

2024-12-10T04:52:45Z CRITICAL current sync strategy failed with: while handling ready block: applying forced changes: cannot find applicable forced change: failed while applying condition: cannot check ancestry: getting header: pebble: not found   pkg=sync

Lots of changes since my approval. Will do another review once the current issue has been addressed.

[dimartiro]

The latest deployment stalled at block #1491033. Apart from lots of networking errors, I found this in the logs:

2024-12-10T04:52:45Z CRITICAL current sync strategy failed with: while handling ready block: applying forced changes: cannot find applicable forced change: failed while applying condition: cannot check ancestry: getting header: pebble: not found   pkg=sync

Yeah, I'm changing the approach and trying with the latest comment from Eclesio