Files
netbird/management/server
mlsmaycon 48d9161056 [management] Stamp proxy peer activity with the database clock
The activity write took a Go-side timestamp, which is exactly what
MarkPeerConnectedIfNewerSession documents as the cause of previous ordering
bugs: a value read before the write can land after a connect that stamped
CURRENT_TIMESTAMP, dragging LastSeen backwards.

The write now uses the database clock like the other status writers, so the
column only ever moves forward. The throttle is unaffected; it reads the
peer already in hand and never needed the write's timestamp.
2026-08-09 07:38:35 +00:00
..
2026-07-23 11:37:09 +02:00
2026-07-23 11:37:09 +02:00