I think so....and we can only assign the executor to the same worker in the subsequent schedule() calls...

and this logic has been here for a long while (at least since 0.8.x), the scheduling mode proposed in this PR is just to relax this constraint