I've been using this package for multiple projects now and have noticed that sometimes when a network error occurs (IP reassignment with dynamic ip for example) during a call, the function never returns and hangs indefinitely. The problem becomes apparent very much in the telegram flexpool block notification bot. I've had to write a watchdog script that restarts the service when the last_blocks() runs into this issue.
I have also noticed the same in the homeassistant flexpool integration I wrote using this library. 
I haven't quite figured out the reason for this. I assume it's the requests lib it's using. Would setting a timeout solve this?
If I can find some time I'll try debugging this further, but for now I'm opening an issue.
I've been using this package for multiple projects now and have noticed that sometimes when a network error occurs (IP reassignment with dynamic ip for example) during a call, the function never returns and hangs indefinitely. The problem becomes apparent very much in the telegram flexpool block notification bot. I've had to write a watchdog script that restarts the service when the last_blocks() runs into this issue.
I have also noticed the same in the homeassistant flexpool integration I wrote using this library.
I haven't quite figured out the reason for this. I assume it's the
requestslib it's using. Would setting a timeout solve this?If I can find some time I'll try debugging this further, but for now I'm opening an issue.