MHSanaei 8dd3b31ee8 fix(node): show the activated first-use deadline on the Clients page ...

With "start after first use" on a node inbound, the node activates the
absolute deadline and the master adopts it into client_traffics via the
sync CASE merge — but the client record (what the Clients page reads) was
only refreshed by SyncInbound from the snapshot's settings JSON. A node
whose JSON still carried the negative duration (stale conversion, older
node build, or a mixed local+node attachment) kept rewriting the record
back to "not started" even though the DB held the real deadline (#5714).

Lift the activated deadline from client_traffics onto still-negative
client records at the end of every node sync, after SyncInbound has run.
Intentional resets back to delayed start are unaffected: editing a client
also resets client_traffics to the negative duration, so the lift's
expiry_time > 0 guard never matches.

Closes #5714

2026-07-02 09:36:07 +02:00

..

config

3.4.2

2026-06-29 20:28:08 +02:00

database

fix(database): stop noisy per-startup errors in the Postgres server log

2026-07-01 23:07:05 +02:00

eventbus

style: adopt golangci-lint v2 and resolve all findings

2026-06-27 15:42:22 +02:00

logger

style: adopt golangci-lint v2 and resolve all findings

2026-06-27 15:42:22 +02:00

mtproto

style: adopt golangci-lint v2 and resolve all findings

2026-06-27 15:42:22 +02:00

sub

fix(sub): use configured spiderX instead of always randomizing

2026-07-01 23:07:05 +02:00

tunnelmonitor

style: adopt golangci-lint v2 and resolve all findings

2026-06-27 15:42:22 +02:00

util

feat: ldap skip tls verify (#5637)

2026-06-28 18:10:38 +02:00

web

fix(node): show the activated first-use deadline on the Clients page

2026-07-02 09:36:07 +02:00

xray

fix(xray): reconcile client auto-disable through the API instead of a forced restart

2026-07-02 09:26:53 +02:00