-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stacktrace recovery doesn't work for suspend main #1328
Comments
Thanks for the report! |
@qwwdfsad do you know a version where it works. Would be nice to see this feature in action. |
I looked in org/jetbrains/kotlinx/kotlinx-coroutines-core/1.2.2/kotlinx-coroutines-core-1.2.2-sources.jar!/commonMain/JobSupport.kt:1131. It seems that the state Empty{Active} isn't the expected one. |
@opensource21 it works in the latest version except for your particular case (with suspending |
As a workaround, you can use |
…s in 'suspend fun main' cases to further improve user experience Fixes #1328
If you clone https://gitlab.com/ppiag/zulipbot, rename application.properties.sample to application.properties and replace Any idea when 1.3 will be released or a beta for a test? |
I took the example https://raw.githubusercontent.com/Kotlin/kotlinx.coroutines/master/kotlinx-coroutines-debug/test/RecoveryExample.kt and add at line 16 a
println("${Thread.currentThread().name}")
, so I getI run it with
I never get an recovered stacktrace. How ever I got
DefaultDispatcher-worker-1 @Example#1
so
-Dkotlinx.coroutines.debug
seems to work.What does I'm missing?
Here my version
kotlin 1.3.41
coroutines.version 1.2.2
The text was updated successfully, but these errors were encountered: