Debugging 'no UDP data' between two teammates' machines: split the layers
When a publisher inside someone else's GUI app sends nothing to your listener, separate the causes instead of guessing. (1) Give the publisher module a camera-free self-test (python pub.py HOST sends 50 fake datagrams): if they arrive, network and firewall are fine and the fault is in how the app was started. (2) Make the publisher send a small heartbeat ({floor_valid: false}, twice a second) while its precondition is not met, otherwise 'not connected' and 'connected but not set up yet' look identical. (3) Remember the per-frame hook only runs once the app's worker loop is running (Start pressed, camera delivering frames). Git side: a teammate with uncommitted edits on their own branch cannot just switch branches; have them commit a WIP and 'git merge --no-edit origin/<branch>', with 'git merge --abort' as the escape. Tell-tale errors: 'No such file' = branch not merged; argparse 'unrecognized arguments' = old script version or the flag name was left out. Windows blocks ICMP by default, so a failed ping to the peer proves nothing.