Premature termination of observation when there is no connection to network

Hi,

The recent addition of posting metadata (commit 1eccb138) has some unfortunate side effects when there is no connection to the server.

https://gitlab.com/librespacefoundation/satnogs/satnogs-client/blob/master/satnogsclient/observer/observer.py#L159

A timeout here does not return an error code but raises an exception, which I suppose terminates execution of the script. Consequently, no waterfall or audio is generated after the observation, and the raw files are left in place.

I think we see the same problem other places as well, i.e. we have an exception instead of a nice error message; however, this is the only place that I know of where it has fatal consequence.

Thanks to @DL4PD for help with triaging this problem.

Edited by Alexandru Csete
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information