Trie prunning async trigger

[ssd04]

Reasoning behind the pull request

Proposed changes

Testing procedure

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

• was the PR targeted to the correct branch?
• if this is a larger feature that probably needs more than one PR, is there a feat branch created?
• if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?

[codecov]

Codecov Report

❌ Patch coverage is 65.85366% with 28 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.54%. Comparing base (1efa373) to head (36405f9).

Files with missing lines	Patch %	Lines
process/block/metablock.go	18.18%	8 Missing and 1 partial ⚠️
process/block/baseProcess.go	82.92%	4 Missing and 3 partials ⚠️
process/block/shardblock.go	44.44%	5 Missing ⚠️
state/accountsDB.go	0.00%	4 Missing ⚠️
...ocess/transactionEvaluator/simulationAccountsDB.go	0.00%	1 Missing ⚠️
state/accountsDBApi.go	0.00%	1 Missing ⚠️
state/accountsDBApiWithHistory.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                     @@
##           feat/supernova-async-exec    #7800   +/-   ##
==========================================================
  Coverage                      77.53%   77.54%           
==========================================================
  Files                            882      882           
  Lines                         123716   123789   +73     
==========================================================
+ Hits                           95919    95986   +67     
- Misses                         21439    21440    +1     
- Partials                        6358     6363    +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR introduces an async trigger for trie pruning (especially for header v3), wiring it through the async headers execution flow and updating the relevant interfaces/mocks/stubs accordingly.

Changes:

• Add PruneTrieAsyncHeader(header data.HeaderHandler) to block processor interfaces and implement it in the base processor.
• Stop triggering shard header v3 pruning from shardProcessor.updateState and trigger pruning from asyncExecution/headersExecutor.
• Add process.GetHeaderWithNonce(...) helper to fetch headers by nonce for both shard and metachain paths.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
testscommon/processMocks/blockProcessorStub.go	Extend async-execution stub with PruneTrieAsyncHeader.
testscommon/blockProcessorStub.go	Extend test stub with PruneTrieAsyncHeader.
process/interface.go	Add PruneTrieAsyncHeader to main process.BlockProcessor interface.
process/common.go	Add GetHeaderWithNonce wrapper that dispatches to meta vs shard retrieval.
process/block/shardblock_test.go	Update pruning test to pass a header (not exec results slice).
process/block/shardblock.go	Remove sync v3 pruning from updateState; change v3 pruning API to accept a header.
process/block/metablock.go	Rename/simplify v3 pruning path and fetch previous meta header on-demand.
process/block/interface.go	Extend internal blockProcessor interface with pruneTrieHeaderV3(header).
process/block/export_test.go	Update exported test helper PruneTrieHeaderV3 signature; add test-only getters/setters for last pruned nonce.
process/block/baseProcess_test.go	Add unit tests for PruneTrieAsyncHeader.
process/block/baseProcess.go	Add async pruning logic with intermediate nonce handling + last-pruned nonce tracking.
process/asyncExecution/interface.go	Add PruneTrieAsyncHeader to async execution’s BlockProcessor interface.
process/asyncExecution/headersExecutor.go	Trigger async trie pruning after execution result is persisted/tracked.
integrationTests/mock/blockProcessorMock.go	Extend integration mock with PruneTrieAsyncHeader.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In this test, execution results are set on header1 (nonce 8), but the method under test is called with header3 (nonce 10). This leaves header3 without execution results handlers, so PruneTrieAsyncHeader(header3) may not trigger pruning as expected and the assertions can become incorrect/flaky. Set the execution results handlers on header3 (or call pruning on the header you populated).

Suggested change

	_ = header1.SetExecutionResultsHandlers(executionResultsHandlers)
	_ = header3.SetExecutionResultsHandlers(executionResultsHandlers)

[Copilot]

getPreviousExecutionResult() uses sp.getCurrentBlockHeader().GetPrevHash() to find the previous header. With the new async pruning flow (including pruning of intermediate nonces), pruneTrieHeaderV3() can be called for headers that are not the current committed header, so this will fetch the wrong previous header and compute incorrect previous root hashes for pruning. Pass the header being pruned (or its PrevHash) into getPreviousExecutionResult() and use header.GetPrevHash() instead.

[Copilot]

If pruning an intermediate nonce fails (e.g. header not found and the loop continues), lastPrunedHeaderNonce is still advanced to the provided header’s nonce at the end. This permanently skips the failed intermediate nonce(s) and they will never be retried in later calls, which can lead to missing trie pruning. Consider only advancing lastPrunedHeaderNonce up to the last successfully pruned nonce, or track/retry failures instead of skipping them permanently.

[ssd04]

added long sequence of headers in tests, it's a long test, but it's easier to be analysed (or changed later on if needed) like this