1. Use IdentityHashMap to avoid relying on hash-code which may require read action for some descriptors
2. Rename one of `getJdiValueForDfaVariable` overloads to `getJdiValuesForQualifier`
GitOrigin-RevId: c3bc4663f2156946c6117eb9bfe947e387a0fcf2
For some reason sometimes there can be different numbers of ending line breaks. Should not be a big issue for this test.
GitOrigin-RevId: f52b527658ef71e0184789c5e261a16a50f70f05
Production session can consume some initial events and replace it with a single `TerminalInitialStateEvent`.
This behavior is not suitable for the purpose of this test at all. So, let's use a low-level session.
Should fix IJPL-188563 and IJPL-189348
GitOrigin-RevId: 25b7494c8dcc9b7e3308bb83268516e2506db644
- CMD+arrow down: jumps down by approximately one page; if the target element is not loaded, jumps to the last available item.
- CMD+arrow up: jumps to the top.
GitOrigin-RevId: 15e4e6445366da55724414670322b46ce2118389
### Issues
* KTIJ-34501 java.lang.Throwable: Don't have a LinkedProjectId for module new_gradle_1749291131663 for HMPP!
### Tests
* com.intellij.driver.tests.idea.buildTools.GradleTest.testGradle
GitOrigin-RevId: 53bb3019c8e40123596fa57eed322c5f4cbc9933
The NPW legacy API allows to skip content entry path definition. However in this generator cannot create project or module, because there are not information about where this project should be created. Therefore, this behaviour is forbidden for Gradle NPW generator. And the contentEntryPath property should be specified explicitly.
GitOrigin-RevId: 05df9a0bdec7953abc349579958cb83a44f1554e
The base NPW step specifies, prepares and validates project location. Therefore it should ensure that the project/module directory is created.
Also, all project file and scripts generators should ensure that the parent directories is created. Because the IO cannot be protected from external modification. And the NPW API cannot guarantee that project/module directory is exists during the whole project/module creation process.
GitOrigin-RevId: e1332ce096846629c6c86234032fbee142dbb7e5
update expected data
update api dump
enable constant refs and imports data collection for java; move default java- and kotlin- analysis strategies registration to dep-graph module
Merge-request: IJ-MR-167023
Merged-by: Eugene Zhuravlev <eugene.zhuravlev@jetbrains.com>
GitOrigin-RevId: e77ef202c42ffad604b62b4d485e53f9572c14a4
makes more sense as it's only used there and makes the dependencies cleaner
removed unnecessary alias from intellij.platform.whatsNew
GitOrigin-RevId: 7d974e1185beb47b048c69a8aece9439ba94b747
Under a flag debugger.async.stack.trace.for.all.threads, getAgentRelatedStack returns async stack trace for any thread, not just for the current thread.
The new method com.intellij.rt.debugger.agent.CaptureStorage#getAllCapturedStacks introduced in the debugger-agent allows to obtain captured stack traces for all the threads.
GitOrigin-RevId: 5bb498afb6bb102ff0e8d3d8ced415d41a3e3e08
The new method com.intellij.rt.debugger.agent.CaptureStorage#getAllCapturedStacks introduced in the debugger-agent allows to obtain captured stack traces for all the threads.
Async stack traces for coroutines are computed in the same evaluation as the dump.
IDEA-366087
GitOrigin-RevId: be52ccd3b391c347536daef0e2567554024bdae3
Introduced new API to get async stack trace for any thread, using the same evaluation context. See `debugger.async.stack.trace.for.all.threads`.
GitOrigin-RevId: 2fa32e7172106895feafda1c5e2f32822d53d941