applyClientFieldByEmail patched only the first inbound that the client_traffics row pointed at. For a multi-inbound client the sibling inbounds kept the old expiryTime/totalGB/limitIp in their settings JSON, and the next SyncInbound over a stale sibling reverted the edit in the normalized records — the Telegram bot's expiry change appeared to apply and then sprang back. Patch the field on every inbound linked to the email, falling back to the legacy single-inbound lookup for clients that were never normalized. |
||
|---|---|---|
| .. | ||
| config | ||
| database | ||
| logger | ||
| mtproto | ||
| sub | ||
| util | ||
| web | ||
| xray | ||