All,
While adding new websocket specific timeouts it seems that active timeouts
are completely broken on master. I quickly tested and verified that they
are working properly as of 5.2.x (which is the branch we're on over here),
so somewhere since then a huge regression was introduced...does anyone have
ideas where it might have happened? If not a git bisect will be required.

Brian

Reply via email to