Leap v3.2.3

This patch release contains fixes for handling forks in state_history_plugin. All users of state_history_plugin running 3.2.1 or 3.2.2 are highly recommended to update to 3.2.3. Downstream consumers of state history data may have been affected by this defect.

state_history_plugin log files remain correct (not corrupt) for affected nodeos versions. However, in 3.2.1 and 3.2.2 there is a possibility when nodeos switches to a new fork, blocks from this new fork will not be sent to existing state_history_plugin connections. The side effects of this will be dependent on the downstream application that is consuming from state_history_plugin, but most likely will result in the downstream application consuming incorrect or missing data for a block because the downstream application will be unaware that a fork has occurred. Users that have populated downstream applications from 3.2.1 or 3.2.2 should repopulate downstream applications with 3.2.3 starting from a block prior to their upgrade to 3.2.1 or 3.2.2.

Leap v3.2.3 Release Notes

Bug fixes

SHiP forking behavior fix

PRs

• (943) [3.2] SHiP Fix forking behavior

The state_history_plugin was not sending updated blocks when nodeos forked. There has been an enhancement made to the ship_streamer_test to generate a fork and verify SHiP sends new blocks on forks.

Contributors

Special thanks to the contributors that submitted patches for this release:

• @heifner
• @linh2931
• @spoonincode
• @stephenpdeos

Full list of changes since last release

PRs

• (893) [3.2] Use block_num for interrupt of start_block
• (928) [3.2] SHiP flush logs on write
• (936) [3.2] forkdb reset in replay since blocks are signaled
• (943) [3.2] SHiP Fix forking behavior
• (953)[3.2] Bump Leap version to 3.2.3

Full Changelog: v3.2.2...v3.2.3