Drop run
and run_in_threadpool
#710
Merged
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.
We're no longer using the backend methods
run
andrun_in_threadpool
within thehttpx
codebase, so this PR removes them.We are however using them within the test cases in order to perform the server restarts.
I've changed things around so that
.restart()
is a standard blocking function (It may as well be, and it runs from a different thread from the server, so it won't block the server itself from shutting down.)However, the tests that use
server.restart()
are currently failing in theasyncio
case. (With h11 errors that the server close event is occuring at a point that it should not.) Really not clear to me why we'd see that with asyncio but not with trio. I think that are resolution here might be that restart should perform a full shutdown, and reopen the server on an entirely new thread, to keep things cleaner?Any thoughts on this @florimondmanca?