Change execution order for single-threaded server #1149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, the single-threaded server runs jobs when
start-job
is called. This PR changes it to instead run jobs whenwait-for-job
is called. The reason to change things is simple;run.rkt
has code that at a high level does:If we run things in
start-job
then we get all the status prints at the very end, once all jobs are done (useless). If we run then inwait-for-job
then we get prints one at a time, like we're suppose to.The PR also has some random minor improvements to the server code.