restrict nove detection to clion
(cherry picked from commit 53618d47e865759d211262860021b420403e88a0)
IJ-CR-155828
GitOrigin-RevId: ae028615bb376b43ba10cd532b0edc7010f25bd6
^PY-77792 fixed
What happened:
`validationRequestor` only tracked the Conda binary path, so when new environments were loaded into the list, revalidation wasn't called, and `selectedItem == null`.
Fix:
Call revalidation on each `comboBox` update.
(cherry picked from commit 26c56b9c44ada5e22f61bbdad828f5b20b04a2d7)
IJ-CR-160864
GitOrigin-RevId: 7ec603dedf5314f8621c8656bd369887cead0b30
- drop builder as it's redundant: all fields are required and don't have default values
(cherry picked from commit 78b99e731fa2332370cc05921b3179136ac166e4)
IJ-CR-160378
GitOrigin-RevId: 0989bb831ab245a555e5a9df15ed97683bc3b09c
### Issues
* IJPL-183135 `Preview in safe mode` opens in normal mode
(cherry picked from commit 7e4fb7dc6eb240caed864f06bc2d350f9f57088f)
(cherry-pick approved by IJ-CR-159977)
GitOrigin-RevId: fa61d834d67b34899492e3b3989d07b14381194c
The createProject and newProject functions create a new instance for the IDE-generated projects (tests or new project wizards). We completely control the project file generation process and can guarantee that we don't add malicious code.
However, the prepareNewProject function can be executed for any project. This function has a different "new project" semantic with the newProject function. Here "new project" means initializing a new project instance without the project caches (.idea). Therefore, it can be used for the existing project without (or with broken) project caches.
### Issues
* IJPL-183135 `Preview in safe mode` opens in normal mode
(cherry picked from commit baf2a12490791dca716801686ba37eb983cc943a)
(cherry-pick approved by IJ-CR-159977)
GitOrigin-RevId: dd0ff1362b160d2d9598fe6d97ee4009cd6b3859
Add a system property that allows enabling trusted checks in the unit test and headless modes. By default, all project in tests are trusted, because all tests are executed in safe environment.
### Issues
* IJPL-172505 Trusted Projects' API is marked as Experimental
(cherry picked from commit 1c50198ca34c28d2e00fcba2774c878e993557b5)
(cherry-pick approved by IJ-CR-159977)
GitOrigin-RevId: d3fa2c34138265744689df1065048fd70d702101
The com.intellij.ide.trustedProjects.TrustedProjects utility object is open for public usage. Other stuff is internal or deprecated in favor of this API.
### Issues
* IJPL-172505 Trusted Projects' API is marked as Experimental
(cherry picked from commit a0f082950faadad8c855cde5090419293aa3646c)
(cherry-pick approved by IJ-CR-159977)
GitOrigin-RevId: 1560d86bb1a22b1e77f84be0e276937f7dc071f2
This is needed because we changed the behavior of MergingUpdateQueue in dfe47c2d63b3489c9e2900f546ea9779f5dea314, and the update that was saving the tree previously is now canceled
(cherry picked from commit 51d29f39d93ab73d003dfbb37bd9ba87466346d1)
GitOrigin-RevId: 948cc9a50c09e7053a3647b8264ca9f0f75a8335
Introduced an identity key for TrackedUpdate. It allows tracing leaked updates event if they have the same equality objects to merge.
### Tests
* org.jetbrains.plugins.gradle.setup.GradleCreateProjectTest
(cherry picked from commit 5cbc7f4d9b49f58061975a4ce5e3cb2d1298d28d)
GitOrigin-RevId: 7b9ccda795affdc8b5397df95a9900dfb91e170b
This would allow abstracting away the computation
of correct receiver types, so that they can
be substituted for cases when there is no
explicit receiver expression
GitOrigin-RevId: cde45523801969f912d15f909a67a60ceeed89ed
`ImportPositionTypeWithReceiver` is
too rigid for some cases, because
there might be no explicit receiver
expression in the code, but we still need
to differentiate between different types
of calls
GitOrigin-RevId: 7ea7c20f0255d957640c106ddc7041ff873445b7
Note 1: Tests are ignored in K1 Mode, and won't be fixed
there.
Note 2: Test for multiple imports at the same time is ignored
until KTIJ-33592 is fixed.
GitOrigin-RevId: 2487b6fb3da0fd313cc61141d7fc3ab13b03e987
