aws / chrony-candm Goto Github PK

I am using this wonderful crate to successfully fetch tracking and source stats info from Chrony, but am running into a snag when trying to fetch SourceData.

Specifically, I get this error:

Custom { kind: InvalidData, error: DeserializationError(Some("message too short")) }

I wanted to drill down a bit more to figure out where this error was coming from, so I copied the chrony-candm and chrony-candm-derive sources into my repo and pointed my crate to the local copies instead, and somehow the error disappeared and the SourceData query began functioning. I am able to replicate this by switching back and forth between a local reference to the chrony-candm crate and the usual reference in my Cargo.toml.

I would like to try to debug this further myself, but I will need to figure out a way to replicate the issue with the crate checked out in a way so I can modify it. Was hoping to see if anyone had thoughts on why this might be happening while I pursue other methods.

In Chrony 4.4, they introduced more fields (hardware counters) + moved the fields to 64 bits.