hiero-ledger/hiero-block-node v0.44.3

on GitHub

Block Node v0.44.3 is a bug-fix release on the 0.44 line. It backports seven fixes from main for operators who stay on 0.44 until their consensus nodes can run BN 0.45. Subscriber sessions no longer leak: a live-only session that closes before its first block is released, and completed sessions are cleaned up even when no new subscribe requests arrive. The publisher no longer stops acking blocks it already stored because of stale resend entries. ExpandedCloudStoragePlugin now reports persisted blocks right away instead of waiting for the next block. Live-sequential days storage no longer stalls at the day boundary because of a stale GCS listing cache.

⚠️ Default change: Block Node socket buffers now default to kernel autotuning instead of a fixed size. A pinned send buffer was capping subscriber throughput on high-latency links. Socket server settings that were previously ignored are now applied. Explicit server.socketSendBufferSizeBytes / server.socketReceiveBufferSizeBytes values are still applied, and the node now warns at startup if the kernel grants less than the configured size.

The CLI blocks validate command now exits with a non-zero status when validation fails.

What's Changed

🐛 Bug Fixes

• fix: backport bug fixes to 0.44.3 (#3717, #3793, #3832, #3770, #3824, #3791, #3757) by @AlfredoG87 in #3875, which includes:
  • fix: refresh GCS listing cache for today AND yesterday in live-sequential by @rockysingh in #3717
  • fix(subscriber): stop waiting for the first live block after session close by @Nana-EC in #3793
  • feat(subscriber): reap completed sessions independent of new requests by @Nana-EC in #3832
  • fix: Clear scheduled resends for persisted blocks so they stop clamping acks by @berryware in #3770
  • fix(cloud-storage-expanded): ExpandedCloudStoragePlugin delays persisted notifications until the next block by @ivannov in #3824
  • feat: Default BN socket buffers to kernel autotune by @AlfredoG87 in #3791
  • fix: blocks validate exits with status 0 when validation fails by @ivannov in #3757

Full Changelog: v0.44.2...v0.44.3