rippled (XRP Ledger server) Version 2.0.1-rc1

This is a release candidate for a hotfix release. There are no new features over 2.0.0; only bug fixes.

Highlights:

• Fixes unbounded memory growth when running the path_find command.
• Fixes a bug that, in some situations, results in online deletion causing delays in persisting records to disk.
• A new line in cfg/rippled-example.cfg sets send_queue_limit = 500. Consider adopting this setting in your own rippled.cfg in the appropriate stanza(s) for configured ws and wss port(s).
  • When the setting is not specified in the config, the default value is 100. At 100, during times when there are >200 transactions per ledger, rippled will disconnect WebSocket clients that subscribe to the transactions stream.
  • Clients receive a disconnected message with code 1008 or a Client too slow disconnection.
  • Using send_queue_limit = 500 fixes this issue.

Testing Credits

• Thanks to @sgramkumar and others for continued testing.

What's Changed

Note: for completeness, the following has been updated to show the changes since 2.0.0, the last stable release (not just 2.0.1-b1).

• Websocket should only call async_close once by @ximinez in #4848
• Improve lifetime management of ledger objects (SLEs) to prevent runaway memory usage. AKA "Is it caching? It's always caching." by @ximinez in #4822
• clang warning about deprecated sprintf usage by @ckeshava in #4747
• Change recommended send_queue_limit to 500 by @thejohnfreeman in #4867
• Add DeliverMax to more JSONRPC tests by @Bronek in #4826
• PR Template - add Type of Change: Performance by @intelliot in #4875
• Proposed 2.0.1-b1 by @intelliot in #4888
• Revert "Asynchronously write batches to NuDB. (#4503)" by @mtrippled in #4882
• Update help message about unit test-suite pattern matching by @ckeshava in #4846
• test: improve code coverage reporting + codecov by @Bronek in #4849
• Proposed 2.0.1-rc1 by @intelliot in #4895

Full Changelog: 2.0.0...2.0.1-rc1