aboutsummaryrefslogtreecommitdiffstats
path: root/spec/util_throttle_spec.lua
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2019-12-07 19:05:10 +0100
committerKim Alvefur <zash@zash.se>2019-12-07 19:05:10 +0100
commit01aea4e5d2256d359690431214e54e4bdf1e2672 (patch)
tree8c397254cf4f1bc92a270cf4309404bffac31e5d /spec/util_throttle_spec.lua
parent9c4ff0b7127ca04f826689fd400bd4dc323922d8 (diff)
downloadprosody-01aea4e5d2256d359690431214e54e4bdf1e2672.tar.gz
prosody-01aea4e5d2256d359690431214e54e4bdf1e2672.zip
net.server_epoll: Add debug logging for delayed reading
In :onreadable, if there is still buffered incoming data after reading from the socket (as indicated by the :dirty method, usually because LuaSocket has an 8k buffer that's full but it read a smaller amount), another attempt to read is scheduled via this :pausefor method. This is also called from some other places where it would be pointless to read because there shouldn't be any data. In the delayed read case, this should report that the socket is "dirty". If it reports that the socket is "clean" then the question is where the buffer contents went? If this doesn't get logged after the scheduled time (0.000001s by default) then this would suggests a problem with timer or scheduling.
Diffstat (limited to 'spec/util_throttle_spec.lua')
0 files changed, 0 insertions, 0 deletions