MHSanaei c3cc8b4374 fix(job): gate ip-limit scan on clients.limit_ip instead of parsing all settings ...

hasLimitIp ran settings LIKE '%limitIp%' and JSON-parsed every matching
inbound's settings blob — and since clients marshal limitIp without
omitempty, every inbound matched, so each 10s scan loaded and parsed
every settings blob in the database (~75MB of JSON at 500k clients) just
to decide whether any limit exists.

It now probes the normalized clients table (limit_ip > 0, Limit(1) count
like depletedCond does), which SyncInbound and the legacy seeder keep in
sync with the settings JSON. Semantics note: a limitIp that exists only
in settings JSON with no clients row no longer enables enforcement — the
enforcement path itself already resolves clients through the same
normalized tables.

2026-07-02 16:24:18 +02:00

..

config

3.4.2

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

database

fix(settings): repair legacy path settings that block every settings save

2026-07-02 13:42:03 +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

test(scale): cover traffic poll, ws payloads, ip-limit job, sub and xray config at 500k

2026-07-02 16:12:46 +02:00

tunnelmonitor

style: adopt golangci-lint v2 and resolve all findings

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

util

fix(sub): default https:// for scheme-less support and profile URLs

2026-07-02 13:47:10 +02:00

web

fix(job): gate ip-limit scan on clients.limit_ip instead of parsing all settings

2026-07-02 16:24:18 +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