Wez Furlong 7f21784537 xfer: fix far-future timestamps on transferred messages ...

A message received via inter-node transfer, on systems hosted on AWS, could
end up with a wildly incorrect far-future timestamp. The underlying mac_address
crate would pick a NIC with the same MAC address as other AWS instances in the
cluster, and that triggered a code path where the collision resolving logic
misinterpreted the timestamp portion of the incoming spool id.

The thing that made this painful was the logic in spool_id.rs: it
misinterpreted the subsecond portion of the timestamp extracted from
the uuid, and due to the way that that field wraps, could produce wildly
inaccurate deltas with a huge multiplier.

As a belt and suspenders treatment, allow the user to influence which
MAC address is selected via the new KUMO_MAC_INTERFACE and
KUMO_MAC_ADDRESS environment variables.

2026-08-25 07:48:50 +01:00

..

src

xfer: fix far-future timestamps on transferred messages

2026-08-25 07:48:50 +01:00

Cargo.toml

proxy-server: add tcp_keepalive option

2026-05-06 21:09:10 +01:00