8c095b9a563e0805b012d526f8955594f890902d
The 2026-10-18 live test on the dev rig showed the opt-in managed ack path cannot work as built: AlarmClient.RegisterConsumer returns -65 alongside the worker's wnwrap reader (the worker then silently falls back to wnwrap), the managed client does not recognise the wnwrap GUID even standalone, and the gateway's GUID arm sends empty identity fields. Replace the docs' claim that the path works with the measured results and tell operators to leave MXGATEWAY_USE_MANAGED_ALARM_ACK unset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Description
No description provided
Languages
C#
48.4%
Java
40.1%
Python
3.2%
Rust
3%
Go
2.6%
Other
2.7%