block finality stops running after synchronization completed with the test-net

[tristanlee]

Description

A new test node get stuck after completion of blocks synchronization with the test-net.

Steps to Reproduce
launch a test node(master branch build) with following cmd:

./target/release/metaversevm --chain testnet \
  --base-path ./chaindata/node01 \
  --validator \
  --unsafe-rpc-external --rpc-methods Unsafe --rpc-cors all \
  --unsafe-ws-external \
  --pruning=archive \
  --name node1

Logs, Errors or Screenshots

2021-12-06 22:00:32 Re-finalized block #0x1e87a8c82d11c62e2e49ed427a743e7b7273617a8aa0e81463ce4a4edd4a2b04 (556503) in the canonical chain, current best finalized is #556544    
2021-12-06 22:00:32 Re-finalized block #0x4b473864548c0e025c99e6c18a898ffc065b32f68250991d93939d16cb3dfc05 (556535) in the canonical chain, current best finalized is #556544    
2021-12-06 22:00:32 Re-finalized block #0x2533db766f68dea6102893bed319273d1b7e93704692605acdcf783ab6c23362 (556539) in the canonical chain, current best finalized is #556544    
2021-12-06 22:00:33 Re-finalized block #0xdb8b4c2568d027b5695fb56c1dfb3baef127c38e2255adc087e27af5fa4a5700 (556544) in the canonical chain, current best finalized is #556544    
2021-12-06 22:00:33 💤 Idle (3 peers), best: #556569 (0x206e…acd6), finalized #556544 (0xdb8b…5700), ⬇ 1.9kiB/s ⬆ 0.7kiB/s 

[aaronzhzh]

yes and also with error message"Header not found" when syncing.

[sylvaincormier]

An observation...
Why are

new-frontiers/node/src/rpc.rs

Line 56 in efce57d

C: HeaderBackend<Block> + HeaderMetadata<Block, Error=BlockChainError>,

and
https://github.com/paritytech/substrate/blob/2651d5cf410700c8a9bbe1b5df54aa9956926b34/bin/node-template/node/src/rpc.rs#L31
Different? (+ 'static)
I will look at other repos and try when I finish building.

[sylvaincormier]

Hi I have tried out the above fix a now get this without encountering the message.
I will make a pull request ask for your review

.