Introduce support for canceling async types in Quarkus Rest

[geoand]

When the underlying connection is closed, we can now cancel the underlying pipeline when an async type is supported.

Question: Should this be configurable? I am wondering because it is not unimaginable that some people might relying on the pipeline being completed in some fire and forget scenario.
Based on the scenario I explained above, I consider this a breaking change (albeit unlikely to break many people...)

• Closes: Support cancelling Kotlin coroutine handlers on connection closing #41705

[calebkiage]

Thanks for putting this together so fast :-) How do I test? Is there a maven repo I can use once the CI is done?

Also, to answer your question, I thought this could be a configurable option.
If the option's default is the old behavior, it won't be a breaking change either.

[geoand]

If the option's default is the old behavior, it won't be a breaking change either.

Very true. If we decide to add one that preserves the old behavior, I'll remove the label.

How do I test?

You need to checkout https://github.com/geoand/quarkus and use the rest-cancelable branch.
Once that is done, you can build the project like so (other options are possible, but this is what I use):

mvn -T 1C -DskipDocs -DskipTests -DskipITs -Dinvoker.skip -DskipExtensionValidation -Dskip.gradle.tests -Dskip.gradle.build -Dtruststore.skip clean install -Prelocations

Then update your project to use version 999-SNAPSHOT while also making sure to use io.quarkus instead of io.quarkus.platform for the Quarkus BOM.

[geoand]

@cescoffier @gsmet what do you think of the breaking aspect of this?

Perhaps we don't have to worry about it as it's clearly a very small niche?

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 3f1fa03.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[cescoffier]

I would. It worry too much. The new behavior is the correct one.