Closed mero64 closed 1 year ago
Hi @mero64 ,
This looks like it might be just a temporary problem connecting to the Telegram server (in order to send the notification messages). Did the problem persist? Are you still seeing this?
Hi, yes, it seems to be a problem reaching the Telegram server. Since it is an external dependency, I think the error should be caught, in case the server is unreachable. Just to make the service more stable. It is very rare (but I guess that depends on Telegrams stability). I haven't seen it again.
As a side note, I got an apartment a few days ago thanks to the flathunter, so thank you!
Hi @mero64 ,
If we catch / suppress the error, we have no way to notify the user / administrator that the notifications are not being sent. We need to be careful only to catch 500 errors and timeouts (and not 4xx errors that might indicate a configuration issue). I think because the issue is rare, and because a flathunter that doesn't send notifications is pretty useless, I would leave this as it is for now. But if you're interested to make a pull request I would welcome that :)
And congrats on finding a flat! We don't get so many user experience reports because people who have flats tend to disengage with the software :) Nice to hear that it helped you.
Closing this - pull requests still welcome.
This error crashed my service yesterday. I was on 014e987, but it looks like the code is still the same (sorry if fixed already).