This change adds a step to the GitHub CI to run the Bazel build
generator script, and then check it has not made changes to any
Bazel build files (ignoring the android submodule, which we do
not care about). If it has, then the committer needs to run the
script locally and commit & push these changes in the PR.
closes https://github.com/JetBrains/intellij-community/pull/3247
GitOrigin-RevId: 00d5e8973d938fd8bb5805ae82d5b32a72f194ff
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.
GitOrigin-RevId: 85a23dbc40c201a247747c14f9651277d6dfddb6
instead of oldParent/newParent, there must be parent installed.
See the corresponding stacktrace:
java.lang.IllegalArgumentException: Argument for @NotNull parameter 'child' of com/intellij/codeInsight/daemon/impl/PsiChangeHandler.queueElement must not be null
at com.intellij.codeInsight.daemon.impl.PsiChangeHandler.$$$reportNull$$$0(PsiChangeHandler.java)
at com.intellij.codeInsight.daemon.impl.PsiChangeHandler.queueElement(PsiChangeHandler.java)
at com.intellij.codeInsight.daemon.impl.PsiChangeHandler.childRemoved(PsiChangeHandler.java:121)
at com.intellij.psi.impl.PsiManagerImpl.notifyPsiTreeChangeListener(PsiManagerImpl.java:509)
at com.intellij.psi.impl.PsiManagerImpl.lambda$fireEvent$9(PsiManagerImpl.java:448)
at com.intellij.psi.impl.PsiManagerImpl.runWriteActionOnEdtRegardlessOfCurrentThread(PsiManagerImpl.java:467)
at com.intellij.psi.impl.PsiManagerImpl.fireEvent(PsiManagerImpl.java:446)
at com.intellij.psi.impl.PsiManagerImpl.childRemoved(PsiManagerImpl.java:334)
at com.intellij.psi.impl.file.impl.PsiVFSListener.filesMoved$lambda$0(PsiVFSListener.kt:586)
at com.intellij.psi.ExternalChangeActionUtil$PsiExternalChangeService.withExternalChange(ExternalChangeActionUtil.kt:59)
at com.intellij.psi.ExternalChangeActionUtil.externalChangeAction$lambda$0(ExternalChangeActionUtil.kt:28)
at com.intellij.openapi.application.impl.AppImplKt$runnableUnitFunction$1.invoke(appImpl.kt:124)
at com.intellij.openapi.application.impl.AppImplKt$runnableUnitFunction$1.invoke(appImpl.kt:124)
at com.intellij.platform.locking.impl.NestedLocksThreadingSupport.runWriteAction(NestedLocksThreadingSupport.kt:999)
at com.intellij.openapi.application.impl.ApplicationImpl.runWriteAction(ApplicationImpl.java:1132)
at com.intellij.psi.impl.file.impl.PsiVFSListener.filesMoved(PsiVFSListener.kt:552)
GitOrigin-RevId: 64101f296637f1c6702d0fdbd16e4f9fc0eb66f3
DockerBinaryPathsProvider's `SuspendingLazy` (`dockerPath`) was created on `Dispatchers.EDT` without a `ModalityState` context element, which prevented the computation from starting. As a result, the Docker connection dialog showed only "Loading..." with no fields.
Use `currentCoroutineDispatchingContext()` (EDT + proper `ModalityState`) when creating the `SuspendingLazy` both for the local `dockerPath` and the autodetected/remote path cache. Initialize the lazy in `init()`.
This unblocks `dockerPath` detection and restores the connection options UI.
GitOrigin-RevId: e1d07dd85f8475f90bd918bcd49c511619196e64
- strange behaviour in meet. It is hard to create a test because this method is called in really rare cases.
GitOrigin-RevId: 042a265817d160f9dd782f92195661e251c24a5b
If text changes inside the prompt after command start offset was set, we need to update it, otherwise features that rely on it (like typeahead) might work incorrectly.
Unfortunately, can't predict how to update offsets when a change happens both in the prompt and command text. So, in this case, offsets will be wrong.
GitOrigin-RevId: bd9ae3e04acd8036a5ea8f9d194d1fb520132146
Let's try to cache the values to implement canNavigate
so it can be safely invoked on the EDT.
This should fix the slow ops in next / prev occurrence.
There's a risk of performance regressions, though,
because now this value will be precomputed for all nodes,
and there can easily be thousands of them.
GitOrigin-RevId: 068f3f99c600024aea1aab9b5eba7e140ca951e3