#185 fixes an issue where a single offline probe would break the whole --latency output due to an error being thrown here, but what's also weird is we exit with a zero status code in such a case. That seems to be the case with all errors - they are ignored, there's no output, and no status code change, and I'm not sure why it's done that way. @radulucut ? I suggest we print error details and exit with 1 in all unexpected cases.
#185 fixes an issue where a single
offlineprobe would break the whole--latencyoutput due to an error being thrown here, but what's also weird is we exit with a zero status code in such a case. That seems to be the case with all errors - they are ignored, there's no output, and no status code change, and I'm not sure why it's done that way. @radulucut ? I suggest we print error details and exit with1in all unexpected cases.