abf272a781
Add logging to trace position data flow from simulator to registry bridge. Verify that positions are correctly received and processed through the complete data path: 1. Simulator API receives node positions via POST /api/simulator/nodes 2. Positions persisted to VirtualNodeStore 3. Periodic 30s sync reads positions from store 4. Registry bridge processes positions (spread geometry for default origin) 5. Positions written to Fleet Registry database Enhanced logging at each step shows: - Sync start with node count - Per-node position processing (default origin vs explicit) - Per-node sync to registry with position values - Registry operations (create/update with positions) Data flow confirmed working. Positions DO flow from simulator to registry_bridge.go to fleet registry. Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bf-1oj7-transformcontrols-analysis.md | ||
| bf-2irz-findings.md | ||
| bf-2r5o-findings.md | ||
| bf-3ifj.md | ||
| bf-3ukb.md | ||
| bf-3y9r.md | ||
| bf-4bhd.md | ||
| bf-5yff.md | ||
| bf-6aif.md | ||
| bf-13s0.md | ||
| bf-28dv.md | ||
| bf-33za.md | ||
| bf-195o.md | ||