Ruslan Ibrahimau (Ibragimov)

Added two more handlers to highlight my issue that I was having with spring-boot 3.1.3. In this version context parameters actually works in handlers, if request parameter name provided explicitly...

Switched to 3.1.3 and this is actually reproducer for the name issue

We have a mixed codebase with and without Spring. We also use Reactor and coroutines. As a common mechanism for handling security and transactions, we use context parameters. Instead of...

Most built-in dispatchers do not exposed as a type: https://github.com/Kotlin/kotlinx.coroutines/blob/master/kotlinx-coroutines-core/jvm/src/Dispatchers.kt#L14 `DefaultScheduler`, `DefaultIoScheduler`, `Unconfined` - internal objects `Main` - property `StandardTestDispatcher`, `UnconfinedTestDispatcher` - functions So it's not realistic to support `FooDispatcher::class`,...

More generic feature would be supporting injection arbitrary `CoroutineScope`, since there is no benefit for tests to inject `StandardTestDispatcher` but not be able to access `TestScope`. And then, if you...

@marcphilipp yes, I think using `runTest` directly make more sense and can be just documented. It's part of `kotlinx-coroutines-test` and user can use any version, so junit do not need...

Same for me, Gradle 9.1.0 Allure Gradle 3.0.0 Configuration with manual `allureAggregateReport` dependencies stop working: ``` Type-safe project accessors is an incubating feature. > Task :buildSrc:checkKotlinGradlePluginConfigurationErrors SKIPPED > Task :buildSrc:generateExternalPluginSpecBuilders...