In order to prevent showing modal progress bar all the time, it's better
to start detection algorithm when we start choosing the interpreter. In
this scenario the progress bar will be show very rarely.
GitOrigin-RevId: 8b2e756e1d46a177ce7dd581520b201c5dd4e897
While NIO has one, it represents local (the one used by `Path`)
separator.
This one represents separator on Eel
GitOrigin-RevId: fd3215ac0dd18861abc00de6e9cd8e66b3b4a797
SVG image with classes doesn't work in Compose which is used as a frontend by Python SDK configuration
GitOrigin-RevId: d84e5418f64d60747fd80a3d8e5a5e88be681c3d
Each tool (uv, poetry) now has `common` and `backend` part. `common` has icons because we need them both on the front and on the back.
We might need to create `front` module also if we wouldn't be able to use icons in compose.
GitOrigin-RevId: 560b5aa67e4e747a1653ad6e4f780301a3fae289
We are slowly moving all tools to the separate modules to register them as EP. On the front we might have `ToolId` only. To map it to an icon we will use EP.
GitOrigin-RevId: 3cd0ad9f8da4a69739c8f632a6305ddd7c29d62d
It is not possible to use topics to access the backend. Only RPC API must be used.
Moreover, registry settings require restart.
GitOrigin-RevId: 965ed41d17350ab0b24b36eb53edf23fba95c4af
Passing lambda to `Logger.assertTrue` just logs the lambda itself,
and does not invoke it
(cherry picked from commit 94ee96615869073e777ccd76ed6f353a9566758f)
IJ-CR-182185
GitOrigin-RevId: 7fce28488cfff2acd11d2def62b10a397bf94207
[pycharm] PY-85729 Post-cherry-pick fixes
[pycharm] PY-85729 Fix stress test on Windows
[pycharm] PY-85729 Fix smoke tests
[pycharm] PY-85729 Add visibility attribute to plugin config
[pycharm] PY-85729 Add a coroutine cleanup test
[pycharm] PY-85729 Add a stress env test
[pycharm] PY-85729 Minor cosmetic fixes
[pycharm] PY-85729 Performance improvement: add debounce to reduce the amount of GC garbage
[pycharm] PY-85729 Fix potential OOM: adjust limits
[pycharm] PY-85729 Fix potential OOM: add cancellation logic for background process observer
The background error process observation logic didn't cancel the coroutines, making them last for way longer than needed. Cancellation logic was added to remedy this.
[pycharm] PY-85729 Fix OOM: Force LazyTree recomposition on tree change
It looks like LazyTree composable hogs memory by keeping track of all the previous trees; this is bad for our use case as any snapshot change to the tree will be saved, causing potential OOM by not freeing the processes. This is fixed by forcing a recomposition on each tree change (via key(tree)).
Merge-request: IJ-MR-183264
Merged-by: David Lysenko <david.lysenko@jetbrains.com>
GitOrigin-RevId: 6a3f71219da1b8577b26d35ce73846685314eb3d
The “Plugin Updates” dialog is needed only to allow the user to select which plugins to update. The actual downloading of plugins should occur afterward.
(cherry picked from commit 0f2d6274707cc99309c905d944ffce7d11461f84)
IJ-CR-182938
GitOrigin-RevId: 0c29e3b446f8b8fb98e848cee83f14241bbbe8f7
1. Filter/Search toolbar size on different zoom levels will be properly sized
2. Toolbar buttons will be right-aligned
3. Packages group headers will have proper sizing on every Zoom level
4. Packages list item will have proper text size when changing IDE zoom
(cherry picked from commit 1b5372491881448a22fa10c4b23df4c3fd1e6f8a)
IJ-CR-183206
GitOrigin-RevId: 1f277e4160811eeb7b4109bef856687777d61c54
The MultiverseFixtureInitializer created a `dirFixture` based on the project base path. The project fixture itself created a `tempPathFixture` for the project directory. This caused the project directory to be deleted twice without a relation.
This commit manually creates the `tempPathFixture` and passes it both to the project fixture and to the directory initialization logic.
Modified to omit logging for 253 cherrypick.
GitOrigin-RevId: a3d613490e0fdfcb32f07aa47c148b695bc49e54
