Fixes
IDEA-343241 Keymap: some actions are not found when opening keymap settings from the welcome screen
GitOrigin-RevId: cd8191e3ba9a3b0e868e757a9838fb5f017a9828
1. reuse `IdeEventQueue.popupTriggerTime`
2. accept any keyboard events as popup triggers.
3. use WINDOW_OPENED event (adds 0-10 ms for me)
GitOrigin-RevId: b67b0aadd5d53366048d68d34e1593795db207dd
Without this fix, at the time of Application Server loading from XML, libraries, loaded before, don't exist
GitOrigin-RevId: 8ef8ae2910bfb71370be97bca16c7de3a9012f62
1. Backend `RunConfigurationsActionGroup` delivers run-configurations from host
2. FrontendThenBackend `AllRunConfigurationsToggle` updates the popup on frontend
3. Drop suspend modifier in `TogglePopupAction.createPopup` to fix IDEA-343454
4. Finalize the GTW-7377 fix
GitOrigin-RevId: fece1c88a36bffb8308f6c18f7d46b830d425847
Use the `INLINE_ACTIONS` key to provide inline actions in a presentation.
Inline actions is a feature of an action presentation, not an action itself. The previous solution is an abstraction leak which could not be easily supported in RemDev, and must not be.
GitOrigin-RevId: 1640e84af3550dd753183b0f93115367ac539a62
Use the `SEARCH_TAG` key to provide an item metadata. It's enough to reimplement the same user-visible logic in `shouldBeShowing`.
Showing or hiding in a popup is a presentation-level feature. The previous solution is an abstraction leak which could not be easily supported in RemDev, and must not be.
GitOrigin-RevId: 1308e091b2986344210bcb3c22d96531584eda01
1. Make it more obvious what each action contains
2. Move more computations to the update session (getChildren)
GitOrigin-RevId: 53350ee2c4d5a413befa4aee4a7972f7e6ae8e9c
1. "All Configurations" toggle in Run Widget triggers dynamic group updates via `updateComponentActions` on click
2. Use `sharedDataSuspend` to avoid "max $maxRetries retries reached" error
GitOrigin-RevId: 7767104106e9cb13049be9379cfe36b427d16ba4
Whether the coroutine name is specified inside `action`, the name isn't seen in coroutine dumps.
GitOrigin-RevId: 7d35e3e82040184975dc63b2400d384b13165470
Some code may stick both due to blocked coroutines or for blocked threads outside the coroutine world. Usage of `ThreadDumper` allows to see both dumps.
GitOrigin-RevId: acce1cd1f8620a94fce0845965438b6187f69437
The file contains functions whose logic is too complicated to just be called a Kotlin-to-Java wrappers.
GitOrigin-RevId: f281a0358e0751d4950254d0529ef406662fb537
There was a false assumption that every code that executes something on WSL sets the working directory via `WSLCommandLineOptions.setRemoteWorkingDirectory`. However, the issue mentioned in the header demonstrates that the git support also sets the working directory via the most usual way, although that way has disadvantages in WSL particularly.
GitOrigin-RevId: 764a6f7e1809b223062779b2f7c3ba71ac835814
