since VFS content storage based on append-only-log, writing/reading of content doesn't need external locking -> could be moved out of locks, there used -> makes the locked region shorter, thus reducing contention
GitOrigin-RevId: f5432f7d4039092b1c333fe21d7b327553668903
Enable the inspection by default but disable AssertJ support because it has too many problems. #IDEA-348567
GitOrigin-RevId: 3dea62277fb224cdc5474e39b28cb4eb94aa8c3c
When retargeting multiple elements in the qualified chain we lose the attached usage infos. #KTIJ-30466 Fixed
GitOrigin-RevId: b2a7310a863b4d34ac8dcf48a046a67ad11dfe00
Instead, the file systems are assigned to WSL distribution explicitly by calling `enableForAllWslDistributions`.
This change removes a race condition between FS enabling/disabling in the benchmark tests.
GitOrigin-RevId: 9c06b1f713068f061fdb8c09080c3c9a81aeee15
As a consequence, `IjentInProjectStarted.execute` suspends the calling coroutine until all IJent server-side applications start. It also looks fairer because starting IJents is required for project initialization.
GitOrigin-RevId: ea7914aced38c3ece0ab8a59e8bde8b51ccd47ce
There were two implementations. One of them did nothing.
It was easily replaced with a nullable class.
GitOrigin-RevId: 0070d7c08c56ef4ccf530d2b13c9d8e1c09585a7
The functions were in `IjentWslNioFsToggler` and they were non-static. It led to problems:
* Checking VM options required to initialize the service `IjentWslNioFsToggler` which initializes the filesystem, causing race conditions in enabling/disabling code in the benchmark test.
* If something has "vmoptions" in the name, it should be in "vmoptions" class, especially when such a class exists.
GitOrigin-RevId: dc228c196799300461b1b287bc5a1428bb0b91f4
It was enabled first in f6d18f61549ec24a2bc7d307743106d9ae0ce2b0 and 4418f0d2049439b2aea050affc0a9d7d8180cc3f, and it was almost immediately disabled in d676fa4790978878885f039805b00b69624d0975 and 217de367786a4191c04679e501ce5a4340398107 due to found issues.
GitOrigin-RevId: 0ccf3e031ba29dab079e1befa61eb77a1aabae47
It was enabled first in 933cc96dbd1899c1e414b23c4819784a2ee1f9a9 and almost immediately disabled in e0dbcd659af1fd5babd844d9f40a9a5f64d9bc23 due to found issues.
GitOrigin-RevId: e0e6d076a7af10b9c17bf0aa97ffd3db3bf50aab
To enable the new filesystem, some tricky VM options must be specified. Just changing the default value of the registry key is not enough.
The new code brings tooling and constants to ease enabling the IJent WSL filesystem in specific products.
`IjentWslNioFsToggler` stops specifying `-Didea.io.use.nio2` because `com.intellij.openapi.util.io.FileSystemUtil.computeMediator` is already aware of the IJent WSL filesystem and starts to use java.nio without the explicit system property.
`IjentWslNioFsToggler` keeps reacting to the registry key changes, but forces its value into the VM options, literally ignoring the state of the registry. It was done on purpose to make the VM options file the only source of truth and to not deal with registry-vmoptions synchronization issues.
GitOrigin-RevId: 6a3c333f841f87cece56ddc26bcbc284cf1a1ecf
Bugs that are mentioned above are caused by a prompt set after the console was converted. This commit adds an ability to add a listener that is called on a prompt update, so our converter can keep it up to date.
GitOrigin-RevId: f9d5b0b6006c3fe95f87bfb65fec3e34b7dedd95
