Cut HELLO if exists in stdout right before checking it to prevent race.
(cherry picked from commit fbf9b0d3e58180d47f6cd88df52893d20685b12a)
IJ-CR-184537
GitOrigin-RevId: 080ab42c4856edc854e92aa3956d2661ea1da00d
Apparently, we have one more problem: we cut too many bytes from tty output. Let's debug it.
(cherry picked from commit 25f2c0d34396558ba9acba24166c5f1e3045c771)
IJ-CR-184537
GitOrigin-RevId: d2aaa62dd549dc52f3074b369da6193a213a788d
Fixes false positive: 'Optional.ofNullable()' with non-null argument should be replaced with 'Optional.of()' when using TypeElement#getAnnotation
(cherry picked from commit 1b3e7f8e4a0d8ef0a611fb644c6b06b137fa9dca)
IJ-CR-184569
GitOrigin-RevId: d132bebf09d2ee872267a20c78b84537dc17dc04
(cherry picked from commit 3906ef8306ce16cbec6de7479cbc4dd51b52d348)
(approved in IJ-CR-184414)
GitOrigin-RevId: 8d01a176667d3bd8494ffd81703343cbc940415f
(cherry picked from commit 23c5fc0157d344a26956ceaa53ab61afd84403e2)
(approved in IJ-CR-184414)
GitOrigin-RevId: 1102a1741f54a9360f30fa280e365649a2cb257d
(cherry picked from commit c5c7ec2466755190f237aee5f73dce12da5c8433)
(approved in IJ-CR-184414)
GitOrigin-RevId: f2aa31d4630eb21a04d78a22d0f6c036862387dc
contains the following manual changes:
update [bazel]: modify test repository URL and commit hash in `BazelTestCases` for `ProtobufResolve`
refactor [bazel]: replace `findAndKillProcesses` with `ProcessKiller` API in integration tests for improved process management
commits from master:
[bazel][Platform UI] IJPL-196093 Search Everywhere: UI tests for LabelSearchEverywhereContributor
(cherry picked from commit e5ee0dd7d05b93b3184b2a99212e56640fef887d)
refactor [performancePlugin]: change screenshots folder creation logic;
When any screenshot folder is created, they get assigned an incrementing counter in front of it. This will allow sorting all the screenshots folders in order they were made.
Merge-request: IJ-MR-182352
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
(cherry picked from commit 803ca46defce9304a9d0e661504e36049decf0db)
refactor [bazel]: remove "build and sync" parameter in `syncBazelProject`ImportBazelSyncTest
(cherry picked from commit 6c1d7b46787edf2b54be948abca97c4013f8a953)
refactor [bazel]: wrap `MoveKotlinFileTest` commands in `ideFrame` to improve test stability and avoid race conditions
(cherry picked from commit c224c58fb339fd804e93c0fe2f36d803f1b85553)
maintenance [bazel]: add ImportBazelSyncTest to verify project import and sync on Hirschgarten
(cherry picked from commit 35de9d9b1ee7e74813b80d697190f66de8a1fd2d)
refactor [bazel] refactor integration tests to use `syncBazelProject` and `waitForIndicators` with explicit 10-minute timeout
(cherry picked from commit 31f67ef862badeb5bf76902ffc4f788dac92ae3d)
[bazel] refactor GolandSyncTest to use `syncBazelProject`; replace `waitForBazelSync` and add explicit indicator timeout
(cherry picked from commit f7ba2f28232d727910c8f2cb5d2b6dc0b2a305fd)
[bazel] refactor BazelVersionUpdateTest to use `syncBazelProject` and wrap it in ideFrame to avoid race conditions
(cherry picked from commit bc248c82da8d46c9f8527e00367abc7883194000)
BAZEL-2658 [bazel] update PyCharm test to use `syncBazelProjectCloseDialog`; improve Git dialog handling
Merge-request: IJ-MR-182198
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
(cherry picked from commit 760c95e81324fe215914f5df8b8839f621b60102)
[bazel] split pycharm test into three to avoid bug with "add file to VCS"
Created by Danil Tereshchenko (Danil.Tereshchenko) via Patronus
Merge-request: IJ-MR-182195
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
(cherry picked from commit a8ba87da73f00db45ee8f451e48d1f518db87bd3)
[bazel] fix performance test race condition;
move commandChain commands into explicit execution inside ideFrame to avoid race condition, where test incorrectly detects import finish on IDE opening.
Merge-request: IJ-MR-182194
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
(cherry picked from commit ef75aa0d34f2a7508fcbc054cc90fb003a08c87d)
BAZEL-2636 [bazel] update pycharm e2e tests with action to close "add file" dialog
(cherry picked from commit d3d8b65cb4d89b6beec1d55c02e8463255e8998d)
[bazel][maintenance] Add `tearDown` method to clean up Bazel server processes in IDE tests
Merge-request: IJ-MR-180571
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
(cherry picked from commit b47af046008dfe6dd8ff81ba2cbe824135256950)
Co-authored-by: Tatiana Elfimova <Tatiana.Elfimova@jetbrains.com>
Merge-request: IJ-MR-184432
Merged-by: Danil Tereshchenko <Danil.Tereshchenko@jetbrains.com>
GitOrigin-RevId: c82378fa28d635f49cf7495b8e859f8e24948b8f
`pluginClasspaths` point to various kotlin plugins. For remote eels (WSL, Docker), these paths are relative to remove machine (i.e `/root/.gradle/..` for Docker).
We now use the eel projects resides on to create correct paths.
(cherry picked from commit a55667ab0828598b6a43b2f56efa02dd0f83b819)
GitOrigin-RevId: 2a491aa4b295d1ee748515e5e245edeb64dbd551
Gradle uses `io.File` as `javaHome` so it doesn't have filesystem info (it is always local).
We set `File("/path/WSL/java")` for WSL (or Docker) on Windows and `File` replaces `/` with `\` (`File.separator`@Windows) so it becomes `File("\path\WSL\java")` following `path` call canonicalizes it to `c:\path\WSL\java` and we end up this nonsense passed as `homePath`.
For the Unix we might have valid path, but local instead of remote: i.e: "/foo" instead of "\\docker\foo"
With this change we use `file.asNio(eelProjectResidesOn)`.
`PackageCheckerBuildGradleKtsTemplateTest` and probably other tests fail on WSL and Docker (on Windows) due to this reason.
(cherry picked from commit 12dffacd43f444930d3eee5222ddd3f707daa852)
GitOrigin-RevId: d7b895e11ffaabd3d976acda101f666234579c99
See `File.asNio` doc.
I mark it `Internal` because we shouldn't encourage external users to use `File`.
`Path` is just convenient: people convert strings to nio on regular basis and always forget the eel.
(cherry picked from commit d754d70476f056b1a5fdf3a9c8e07e1cd5881c8a)
GitOrigin-RevId: e62d89361c5ce33f3afb7c560473758dc1bc85b7
Legacy code might contain `io.File`, then it does
```kotlin
val file = File("c:\\windows")
val parts = file.split(File.separatorChar) // ['C:', 'Windows']
EelPath.build(parts, windowsDescriptor)
```
(cherry picked from commit 85fffa83b3e47a498008d1e120749bdd030b74a5)
GitOrigin-RevId: 0401c9e895a8940684cfab1634eb05b1460604de
When a new task is created because the model has been
updated, it's put into the runner state flow, which causes
the collector to trigger. This sometimes causes
the collector to run the previous task again.
Add a test and fix using distinctUntilChanged
to prevent processing of the same task.
(cherry picked from commit 28c51d65c596021076d206a551bbcb2482f46fd7)
IJ-CR-183360
GitOrigin-RevId: 289eaa30dfcc1e2d28eea936cbf33bab3754851e
Because of this lacking plus, only a part of the message
(thankfully, the most important one) was logged.
(cherry picked from commit 14058e6abe331d2bad984f2ca2bcf10f9d4f94a7)
IJ-CR-183360
GitOrigin-RevId: 24f663879defc3aa018fd4842d6a89c08cf572c5
add test for 30s nes tracking code
(cherry picked from commit 8d1f0d3dc4012f3061314eb91e6ab6a82f9fdbe0)
(cherry picked from commit c611b6324630c97c0cf901045263bd77b9b4a492)
IJ-CR-183880
GitOrigin-RevId: 530a64c8f5d0f7ea1d6d2eea8233472873e1a4d8
Tests that revealed the bug:
K2GradleQuickFixTest.testEnableUpdatedAnnotationDefaultingRuleField
K2GradleQuickFixTest.testEnableUpdatedAnnotationDefaultingRule
(cherry picked from commit e4b52fad1a27c613ae31749314182b3efd43c243)
IJ-CR-183467
GitOrigin-RevId: 05d63bb2a0895693ad62ef61b63583107f920435
`testBreakInFinallyBlock` and `testReturnInFinallyBlock`
were testing vs. latest language level, so apart from
the compatibility warning (for which these tests are
intended) - a corresponding syntax error was captured
I made these tests to use a specific language level
so they only verify the correctness of the compatibility
inspection and introduced four tests in `PythonHighlightingTest`
to capture the syntax error
(cherry picked from commit 254570dc4d5022176590377eaf8ea6a08917937a)
IJ-MR-182362
GitOrigin-RevId: fb9c92923820b370672451c5753ee24bdd5a4570
This runs through steps 1–5 of the releasing-guide.md:
* Bump Jewel version to 0.32.1
* Bump Gradle IJP to 2025.2.5
* Update Metalava baselines, create 0.32.1 dumps
* Write release notes
This also improves the releasing guide adding a bunch of useful info that was missing.
(cherry picked from commit 1501af389cc7207c563b9e87dbe800f1fa08032f)
IJ-CR-184089
GitOrigin-RevId: e024a98aea2e3af18a02a726f77364b1d5926d17
It's needed for LLM-20727 LLMBuildTarget: Provide same release compatibility
(cherry picked from commit 2fa278a18d97adb01fba60b5929227cc899e8995)
IJ-MR-184165
GitOrigin-RevId: 3fb9032e7b5b33d585e52381819dba3692882777
To ease the migration to an explicit plugin dependency in the future
(cherry picked from commit e11b156081e50c072558b75285cdbe965e5db47f)
IJ-MR-184154
GitOrigin-RevId: 60ff0daa18b45bd246e13ec832bdca2180eb18f0
