Fixed evaluation.result event. Note, the statistics were correct for the analysis.compilation.result
IDEA-366380
(cherry picked from commit 90b8f35bc6b9e8c08ef06b965088c509fc17d3c0)
Merge-request: IJ-MR-153908
Merged-by: Alexey Merkulov <alexey.merkulov@jetbrains.com>
GitOrigin-RevId: 47c80ce393305490a467cba3cd743f8b6c343218
Otherwise, `org.jetbrains.kotlin.idea.testGenerator.all.AllTestsGeneratedTest.testAllTestsIsUpToDate` fails with an error like:
```
com.intellij.platform.testFramework.core.FileComparisonFailedError: 'GradleBuildFileHighlightingTestGenerated.java' is not up to date
Use 'Generate Kotlin Tests' run configuration to regenerate tests
at org.jetbrains.kotlin.testGenerator.generator.TestGeneratorKt.write(TestGenerator.kt:156)
at org.jetbrains.kotlin.testGenerator.generator.TestGenerator.write(TestGenerator.kt:72)
at org.jetbrains.kotlin.testGenerator.generator.TestGenerator.write(TestGenerator.kt:32)
at org.jetbrains.kotlin.fe10.testGenerator.Fe10GenerateTestsKt.generateK1Tests(Fe10GenerateTests.kt:172)
at org.jetbrains.kotlin.idea.testGenerator.all.AllTestsGeneratedTest.testAllTestsIsUpToDate(AllTestsGeneratedTest.kt:10)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at junit.framework.TestCase.runTest(TestCase.java:177)
at junit.framework.TestCase.runBare(TestCase.java:142)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:130)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at junit.framework.TestSuite.run(TestSuite.java:236)
at com.intellij.TestAll.runOrCollectNextTest(TestAll.java:399)
at com.intellij.TestAll.run(TestAll.java:280)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at junit.framework.TestSuite.run(TestSuite.java:236)
```
GitOrigin-RevId: c8a0adce00acd8196ac923bf62425f682be70931
The original commit: 1776b92a
Instead of stepping from create to invokeSuspend method of the copied lambda, set a breakpoint into invokeSuspend and resume:
1. First set a breakpoint into `create` method of a given lambda.
2. Get the copied lambda instance.
3. Set a breakpoint into invokeSuspend of the new instance and resume.
IDEA-348340
Merge-request: IJ-MR-147058
Merged-by: Maria Sokolova <maria.sokolova@jetbrains.com>
(cherry picked from commit b190050f086880b02de10a29b5fb61175162348b)
IJ-CR-147164
GitOrigin-RevId: 151051226642470f8e1401d1d82a7a0ca2cd146d
* Step into invokeSuspend for suspend lambdas + check coroutine filter
* Step into create for async coroutine builders, check lambda id and step to invokeSuspend
Merge-request: IJ-MR-141083
Merged-by: Maria Sokolova <maria.sokolova@jetbrains.com>
(cherry picked from commit 1776b92aa566cf51d8f6e79d338c86fc37b2255e)
IJ-CR-147164
GitOrigin-RevId: c16625bfa2ed13e321f7c849357f40ec89dacaba
Before we count as problems the incorrect code fragments which come a lot from watches
IJ-MR-146596
GitOrigin-RevId: 5302ff7c05b47b7430e8f4d05c974cc690ffe9e1
* broaden code fragment type to be able to implement non-java evaluators
Merge-request: IJ-MR-145790
Merged-by: Maksim Zuev <Maksim.Zuev@jetbrains.com>
GitOrigin-RevId: 096badbd7e76b2c8065867349e0839452b683ab4
In Java, the engine can precisely identify the compiled names of classes for the required line. So the check will tell for sure that run-to-cursor will fail. But in Kotlin, the code generation can produce different compiled class names depending on options. It is not easy to be sure in the names while debugging. So better to try to execute run-to-cursor command anyway.
GitOrigin-RevId: 7332655691bb853355af825238c32b4d21d06989
