verified that warp hang is due to faulty slowloris prevention timeout
This commit is contained in:
parent
bf46e6f15d
commit
3e261a4dcb
1 changed files with 4 additions and 1 deletions
|
@ -28,7 +28,10 @@ Hypotheses:
|
||||||
repeated hits to update the alerts? I added a settingsOnException handler
|
repeated hits to update the alerts? I added a settingsOnException handler
|
||||||
that logs all exceptions, and ThreadKilled is happening several times.
|
that logs all exceptions, and ThreadKilled is happening several times.
|
||||||
The only place in Warp that kills threads is due to a timeout installed
|
The only place in Warp that kills threads is due to a timeout installed
|
||||||
for that.
|
for that.
|
||||||
|
|
||||||
|
**Verified** Bug filed upstream: <https://github.com/yesodweb/wai/issues/146>
|
||||||
|
|
||||||
* Something deep in git-annex, such as the inotidy code, could be
|
* Something deep in git-annex, such as the inotidy code, could be
|
||||||
preventing a web server thread from running. But then why do other
|
preventing a web server thread from running. But then why do other
|
||||||
tabs and other web browsers work while it's stuck?
|
tabs and other web browsers work while it's stuck?
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue