Thanks for the error report. I've actually experienced this error myself on several random occasions and having traced it through in great depth am confident I understand its source, but infuriatingly cannot ascertain its cause. Indigo uses the
lsof binary to ascertain which ports are in use on the system prior to starting a stack (as well as several other circumstances). Apparently that's an extremely difficult thing for the system to tell me 🤷♂️
124 is basically a time-out error. Even when Indigo throws that error I can run the exact same lsof command in the terminal and it's usually fine. All I can ascertain thus far is it possibly has to do with how long since your Mac restarted and/or how many processes are using ports, both of which presumably influence how much work lsof has to do to gather the requested port info.
Ultimately I would like to replace lsof entirely for this purpose — but given that it's my third attempt to request port information reliably from macOS I'm running low on ideas 🙂 It's a priority for me once v1 is out the door.
Hopefully it's a temporal issue for you as it was for me — let me know if not.