dev-mainnet not signing Cardano transaction after full import

[jpraynaud]

Why

We have noticed that following the full import of the Cardano transactions in the dev-mainnet network, the certification of the transactions stopped after a few successful signatures.

After investigation, it appears that the aggregator of the dev-mainnet network is missing a row for a block number in its database (confirmed with the testing-mainnet network), which causes the mismatch of signatures:

+------------------------------------------------------------------+--------------+-------------+------------------------------------------------------------------+
|                         transaction_hash                         | block_number | slot_number |                            block_hash                            |
+------------------------------------------------------------------+--------------+-------------+------------------------------------------------------------------+
| 58808ad93c3fb337a91bac2cda44f47a06611e1c797d8cf7d06ed31dcec4b2eb | 10641870     | 130823807   | 8ef8d030154695569b7d8a2c0074c5a340b7d4224773dac054877224cbfffd35 |
+------------------------------------------------------------------+--------------+-------------+------------------------------------------------------------------+

We have also noticed that the problem occurs only when the import is done very close from the tip of the chain, which is probably the source of the problem. An analysis from the logs of the aggregator showed that the problem is likely due to bounds management in the ChainReaderBlockStreamer::get_next_chain_block_action.

What

Investigate and fix the problem.

How

• Investigate the problem
• Fix the problem by fixing the handling of the above threshold of the ChainReaderBlockStreamer::get_next_chain_block_action