When node-ssdp binds to a socket, it adds an error listener. In that listener, the error is only logged, but there is no public API to bubble up the errors in the socket.
We were speculating that this isn't probably a very common error scenario in real life cases, but this issue is as a reminder to double-check what would be a better way of handling this (compared to how we currently handle it, which is ignoring the potential errors).
The text was updated successfully, but these errors were encountered:
When node-ssdp binds to a socket, it adds an error listener. In that listener, the error is only logged, but there is no public API to bubble up the errors in the socket.
We were speculating that this isn't probably a very common error scenario in real life cases, but this issue is as a reminder to double-check what would be a better way of handling this (compared to how we currently handle it, which is ignoring the potential errors).
The text was updated successfully, but these errors were encountered: