Mélodium 0.10.4: bounding memory under reporting load
Mélodium 0.10.4 is out. Like 0.10.3, nothing changes in the language; this release closes two ways the engine could grow memory without bound under sustained execution.
Debug level no longer defaults to Detailed
Execution debug level was hardcoded to Detailed, which cloned every transmitted payload into debug events. On byte-heavy streams, that could grow memory without bound. It now defaults to Basic when something will actually consume debug events (a --debug path given, or --api-report enabled) and to None otherwise. Use the new --debug-level option to override it.
Bounded report channels
The internal log and debug channels feeding --api-report are now bounded, as a last-resort safety net, now that report_logs and report_debug always drain promptly regardless of how the reporting endpoint behaves. The bound is overridable via the MELODIUM_REPORT_CHANNEL_CAPACITY environment variable.
Full details for every crate are in the CHANGELOG . As usual, upgrade with cargo install melodium or grab a prebuilt binary.