Chain connector plugin should be able to save data on every new block in order to create CCUs
Actual behavior
While syncing, Chain connector plugin is missing some data to save and hence resulting in missing data to create CCUs. This happens especially when the sync is longer (more than ~500 blocks) and a block is processing more than 5-6 blocks per second, the new block handler event on the plugin misses to save info for some blocks.
Steps to reproduce
Sync a node with Chain connector plugin enabled which is more than 500 blocks behind the current height and check chainConnector_getBlockHeaders endpoint if the data is saved for all the heights.
Which version(s) does this affect? (Environment, OS, etc...)
Expected behavior
Chain connector plugin should be able to save data on every new block in order to create CCUs
Actual behavior
While syncing, Chain connector plugin is missing some data to save and hence resulting in missing data to create CCUs. This happens especially when the sync is longer (more than ~500 blocks) and a block is processing more than 5-6 blocks per second, the new block handler event on the plugin misses to save info for some blocks.
Steps to reproduce
chainConnector_getBlockHeadersendpoint if the data is saved for all the heights.Which version(s) does this affect? (Environment, OS, etc...)
6.0.1