This patch release contains a bug fixes for a few small edge cases, several test fixes, and documentation updates.
Previously, there was a risk of including expired transactions from the very last call of clear_expired_input_transactions which could lead to generating incorrect snapshots and integrity hashes.
The replay optimization that skips recording transactions within the dedupe list had a risk of leaving the index in an inconsistent state. After some testing, the performance of the optimization being somewhat negligable justified it's removal instead of investing time in refactoring.
Previously, when a transaction was rejected due to too many transactions in progress, that message would only get logged in a Now, the first time a transaction is rejected due to too many transactions will be periodically logged as a warning in Previously, when the resource monitor exceeded its configured threshold, it would be logged as a warning. This has been updated to log as an error in order to prompt action by the operator.
Special thanks to the contributors that submitted patches for this release:
Full Changelog: v3.1.2...v3.1.3
Leap v3.1.3 Release Notes
Changes
Clearing expired transactions before generating a snapshot and integrity hash
Removal of replay optimization
Dropped transactions when overloaded logged as warning in nodeos
debug logging level.
nodeos at an interval of 1 second or more to escalate visibility without spamming the logs.
Use error log instead of warning log when resource_monitor exceeds threshold
Further details on changes since last release
Contributors
Full list of changes since last release
PRs