Fix scheduling bug
Summary: Noticed this while debugging other timerwheel changes. Scheduling new events in callbacks may result in us *running them right away* if they land in a bucket we are currently processing. Instead, round up all the timeouts, then run them separately. This means you can never schedule a timeout that will run immediately (0ticks), but that's probably fine. Reviewed By: yfeldblum Differential Revision: D3679413 fbshipit-source-id: 7e18632f23ea33c072c2718e30b378641895b094
Showing
Please register or sign in to comment