@nico The loop isn't a normal loop. It is generator based i.e it iterate only when there is a value available other wise it stay blocked.
for events_iterator in [
…
@nico Timeout isn't deterministic. i.e it don't come when a lot of requests are coming. So, we can't do that
@nico I am not sure yet about removing the timeout mechanism and moving the maintenance code inside i.e handling of user's request, because it is entirely possible that user's don't make any request…
Thanks. Yes, it doesn't make sense in scheduler.
Removed, although still have some concerns. See the above comment.
changed milestone to %1
closed via commit 74e2168529890f54fcb3ecaa38657640b8a6f059
closed via commit ec447e0dc4a28e29de11f269c1e42bf39d7ed11a
cdist-style docs can be generated since 9f4a85901ef8d58e95924dd9f584ca6437934030. I have yet to auto-deploy them somewhere.
mentioned in issue cdist#853