MHSanaei b40f869f2a fix(node): keep client/inbound edits working when a node is offline (#4923, #4931) ... Node-backed client and inbound edits no longer hard-fail when the backing node is offline or disabled. Edits commit to the panel DB immediately and reconcile to the node when it reconnects (eventual consistency); the panel is the single source of truth for desired config. - Add Node.ConfigDirty/ConfigDirtyAt; mark a node dirty when an edit commits without reaching it (cleared via CAS on ConfigDirtyAt after a full reconcile). - nodePushPlan() reads node state fresh from the DB, skips the push for offline/disabled nodes (no 10s hang), and treats push failures as non-fatal across every mutation path (client add/update/del + bulk + attach/detach; inbound add/update/del/toggle/resetTraffic). - ReconcileNode() pushes the panel's desired config to a node on reconnect (refreshing the remote tag cache first) and prunes node-side orphans; runs before the traffic pull in the node sync job. - While a node is dirty the traffic pull applies only up/down deltas and node-initiated disables, never overwriting desired config from a stale node snapshot. - Surface a non-blocking 'saved; will sync on reconnect' warning to the UI. Validated with a two-panel Docker E2E: client delete/update, attach/detach, and inbound add/delete all reconcile correctly offline -> reconnect.		2026-06-05 02:26:57 +02:00
..
local.go	Feat/multi inbound clients (#4469)	2026-05-19 12:20:24 +02:00
manager.go	feat(nodes): traffic-writer queue, full-mirror sync, WS event fixes	2026-05-10 16:25:23 +02:00
remote.go	fix(node): keep client/inbound edits working when a node is offline (#4923, #4931)	2026-06-05 02:26:57 +02:00
remote_test.go	fix(inbound): re-derive auto tags on edit and keep node tags consistent	2026-06-01 05:08:29 +02:00
runtime.go	Feat/multi inbound clients (#4469)	2026-05-19 12:20:24 +02:00