Pitot gets stuck when /dev/ttyAMA0 does not exist #15
Description
Reproduced on Raspberry Pi without /dev/ttyAMA0, running RUST_LOG=info target/debug/pitot.
Seeing the following output:
INFO:pitot::sensor::gnss::ublox: trying port /dev/ttyAMA0
and then stuck for at least 2 min (did not try longer). Was expecting it to display unable to find any Ublox GPS in the next line after a few seconds. I think serial open might not be timing out.
This might be ok for now but will block pitot from searching for following devices when they are added in the device list.