Behavior was changed during refactoring in `b405b4f4` - `ExecUtil#setupNoTtyExecution` was not setting `-w` flag
(cherry picked from commit e545ef38fee1f3c657347365b0ddb88c45e7bee7)
IJ-MR-172040
GitOrigin-RevId: 9e2385c4bde972690208ce143f31d6cee7da6b63
Previously, it was reachable by strong references: `ShellProcessHolder` -> `EelProcess` -> `PtyProcess`
(cherry picked from commit 97482730f9495ef8ee946e95f16483e906b5fae2)
IJ-CR-171234
(cherry picked from commit a65d3bb4561302d91449f283211341fb33375bd9)
GitOrigin-RevId: e6c64ef9e4ec82c5bf335f896e15089ecf18d311
This will terminate a running command in the shell.
(cherry picked from commit 1467c1ea7afadaf2e70bec7f26c13fd0ab6a31f4)
IJ-CR-171234
(cherry picked from commit da03f7d3bae6d52a6310b5cf17d6d161eb82eac8)
GitOrigin-RevId: b73a2ebcb0551a29d492e7df6505296cc373ba0a
* consider a repository of a selected branch/tag during navigation
* extracted VcsLogNavigatable from BranchesTreeModel
(cherry picked from commit 447f0764c9db150f2d238be25595198305e410e1)
IJ-MR-171997
GitOrigin-RevId: b02506a9a4824f75ec24bdf272bda390345f43b9
Since `380f9a52` `GitCompareBranchesFile` is marked as invalid, but still present in `GitCompareBranchesFilesManager.openedFiles`
(cherry picked from commit a97ec3790515de11cd1b487dfb26756ec77b9e57)
IJ-CR-172001
GitOrigin-RevId: eb20232bc7d0e825a35bb6607844e4b129520baa
This way `EelDescriptor` will be located only once by `Path`.
(cherry picked from commit 0d301c984f1defa674bee231843a80c5d28c9831)
IJ-CR-170679
(cherry picked from commit b16369486ba5f7ce6fbd5cdd17ccc7bb992ed6ff)
GitOrigin-RevId: 916f0bbaca69b15510314330cc17756830eca331
This is a flaky bug: in the case of the second and following debug sessions, the Jupyter Debugger stops at the random place at the debug beginning.
In Python Debugger, we add to threads an additional attribute called additional_thread_info.
The debugger's additional_thread_info stores the current execution state (run/suspended) and step commands.
**When these values weren't cleared after a debug session ended,**
threads with "suspended" state would carry over to the next session, causing it to stop immediately upon start.
Fixed by properly resetting threads' debug state between debug sessions.
(cherry picked from commit ba23933f616c79f9a9e0307f0830f53eebc84ccd)
GitOrigin-RevId: a24425601b0e6a5a497cf974e4a0b4d10e947dab
* Added a new event in the JupyterFeaturesCollector. This event logs what kind of debugger was used.
* Minor refactoring: in the JupyterPyFeaturesCollector class unified formatting and fields names.
* In the PyStatisticTools.kt, fixed the inspection's warnings about an absence of returned types.
(cherry picked from commit 1810e33879ff4d6a40232b28270fd9972480703b)
IJ-CR-171871
GitOrigin-RevId: d2dcdd0df39063d19584840dc2b34fd63b3d379e
* Removed the unnecessary class cast
(cherry picked from commit 11b3449353f1e0f97bfb777d4c4a1b729608ebd5)
IJ-CR-171871
GitOrigin-RevId: 6067c7443c5bdff48123a20c09f6db3c365421ec
`com.intellij.queryComplexity` plugin declares dependency on `com.intellij.modules.sql` plugin alias using `depends` tag in its plugin.xml descriptor. That alias is now declared in a `intellij.database.sql.core.impl` content module in `com.intellij.database`. Before, queryComplexity plugin may be processed in `PluginSetBuilder.computeEnabledModuleMap` before the database plugin, and fail to load because the plugin alias wasn`t registered in `enabledPluginIds`. Now an additional edge in the graph is added in such cases, similar to the case with `dependencies` tag, to ensure that modules are processed in the proper order.
(cherry picked from commit dd202cca60cbee6dce21f73455f4db518f3223e2)
IJ-CR-171496
GitOrigin-RevId: 6fec034550a05642433aad76b3994573c954998b
We will use platform MCP server as a replacement of our smart-functions with duplicating functionality. Also added filter to enable only verified tools
GitOrigin-RevId: 58f2dab68f92693788da62ba127747e98c981c6e
Do not allow automatically scrolling up, only scroll down.
The exception is the case when the cursor returns to the top of the screen (for example, after `clear`) - we have to make it fully visible.
(cherry picked from commit 3ac295a8835cb447ec194844eca817d522be0755)
IJ-CR-170899
GitOrigin-RevId: 906fd9ebad931a0d66fac8787b889235eca92cae
Do not take cursor position into account when adjusting the scroll position if it is not visible.
(cherry picked from commit 94ecd04160476f1b37bb4a14443d0fdc100b2eb1)
IJ-CR-170899
GitOrigin-RevId: c535e8c6e668b4c5d63661a663d524f2dccfd448
- fix missing return type when last statement is a return statement
- add/adjust tests
- add missing null annotations
GitOrigin-RevId: 8fed189d0130c3b41a5f17a3324684a29b39c0ef
