KTOR-9054 Fix application call coroutine context #5170
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.
Subsystem
Server, Netty
Motivation
KTOR-9054 Netty:
applicationandcallcoroutine scopes share the same job instance since 3.3.0Solution
Reverted mistake made in #5070 where I assumed the engine call would follow the job hierarchy and the pipeline context did not, but it is in fact the other way around. It seems the change was not necessary for the auto-reloading fix so it should be fine.
I also included a test to ensure that call coroutine jobs are children of the application job and found this isn't the case all the time, so I fixed the standard Jetty engine and ignored other tests to mitigate impact. Logged a follow up issue KTOR-9058 to fix CIO.