Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Expected behaviour when catching TimeoutThread? #602
In an application I am currently debugging a response handler catches all exceptions via
`catch` \(e :: SomeException) ->
and then logs the expection and continues to do it's work. While I know that this is bad coding and should be fixed right there, I was wondering what the expected behaviour of warp for this kind of situation would be?
Correct me if you think otherwise @kazu-yamamoto, but I think we do not currently handle this case well in Warp. With this code, I believe today you would end up blocking the slowloris protection and the connection would remain open. I think we need the following improvements in Warp: