多接点同步存在问题

[timBen9527]

我在A节点为面板总管理，在B节点创建了入站信息，第一次同步没问题，但我在B节点改变端口等，在A节点无法更新

[shenaba]

Thanks for the report — this was a real bug, and it is now fixed on main (#197).

What was happening: when you import (adopt) an inbound from node B, the master panel A stores a snapshot of it in a local replica row. Nothing ever refreshed that snapshot, so any edit you made on B afterwards — the port, but equally TLS or transport settings — never reached A. Worse than the stale inbounds list: A's subscription links are generated from that snapshot, so A kept handing your users a port the node no longer listens on. The only workaround was to remove the replica and re-import, which unassigns every client from it.

The fix: reconciliation now re-pulls each adopted inbound from the node and rewrites the replica row when it changed, then regenerates the [node] subscription links from it.

When it takes effect: a change made on the node cannot notify the master, so it converges when you press the node's sync button, on any reconcile triggered by a master-side change, or at worst on the hourly drift sweep. Press sync if you want it immediately.

One case still not covered: if you rename an inbound's tag on the node, the master keys the replica by tag and cannot recognise it any more. Changing the port, TLS or transport is fine — only a tag rename. If you need to rename a tag today, remove the replica on the master and re-import it. Tracking that separately.

The fix will ship in the next release.