ClientService.Update only wrote most editable fields to the clients table
inside the per-inbound loop (UpdateInboundClient -> SyncInbound), so a
client with no attached inbound — the external-links / remote-
subscription client — silently dropped subId, totalGB, expiryTime,
limitIp, tgId, comment, reset, flow, security and the credential fields
on edit. Update still returned success, so the panel showed a saved
toast while the row was untouched. email/enable/group_name/ad_tag/reverse
already had dedicated unconditional direct writes that covered the
no-inbound case; the rest did not.
This was a known failure shape: commit
|
||
|---|---|---|
| .. | ||
| config | ||
| database | ||
| eventbus | ||
| logger | ||
| mtproto | ||
| sub | ||
| tunnelmonitor | ||
| util | ||
| web | ||
| xray | ||