socket hangs on "<station>.status" if request for URL gets no response from http.input source

[liquidpeter]

We are using telnet command station.url [url] to dynamically set an HTTP input URL.
Afterwards we use station.status to check if the url is polling, matchs to the URL set before, and further checks.
In case a HTTP request to the URL gets no response from audio stream server, the status command in telnet interface will hang and not return. This will result the client in hanging, too.
A workaround at client is to read from liquidsoap telnet interface using a timeout. From user view it would be better if the status command returns after some time, if connection status cannot be received.

[toots]

Hi,

Is the station.status a custom telnet command? We have asynchronous functionalities that it may be possible to use here..

[liquidpeter]

source.status is the built-in input.http telnet command.
In opposite to source.url it does not just contain the URL value, but additionally the current status like "polling" or "connected". If the source URL does not respond, the "status" call will hang.
source.url works, but it does not contain the current status nor the URL.
The issue occurs if the source stream hangs and you can connect but get no response from it.

an example script:

`set("log.stdout", true)
set("log.file", false)

set("server.telnet", true)
set("server.telnet.port", 1234)
set("server.telnet.bind_addr", "127.0.0.1")

radio = input.http(id="station", "http://127.0.0.1:8000/radio")
radio = audio_to_stereo(radio)
radio = mksafe(radio)
output.dummy(fallible=true, radio);

$ telnet localhost 1234

station.status
polling
END

station.url http://not-responding-url:8000
Done
END

station.url
http://not-responding-url:8000
END

station.status
... hangs ...`

[patrykkrz]

I have the same problem in version 1.3.3.
How to avoid this? Do you have a solution for this?

[toots]

Thanks for the report and insisting. I have just pushed a fix that will go with the next 1.3.7 bugfix release.