Enhanced the `Test-Excluded` function to better handle directory paths by checking if the exclusion is a directory and ensuring it has more path segments than the excluded path. This improves the accuracy of determining whether a path should be excluded.
(cherry picked from commit e494da49d0722bbd599704d9e51c9d37e9a37987)
IJ-CR-149682
GitOrigin-RevId: d76f36bd247b9455f1c60d216a10f369d0b0f333
Version version (x86) was used by accident
(cherry picked from commit 587b58a59e9229217a99c7f4798763bd7f7c0a7f)
KT-CR-18867
GitOrigin-RevId: 7c24c5983482b19c1856608fc47671075b5a15f1
1.When remote side socket is closed, `SIGPIPE` might be sent. We must ignore and exit correctly (we can't die as we might accept more connections)
2. shutdown and close sockets will inform remote side that socket is closed. Without it, remote side may not notice anything until the next write.
GitOrigin-RevId: 51a6204651e49f63ac8b52d9e3e1e4928007c3ff
Due to https://github.com/microsoft/WSL/issues/10718 `SHELL` var is set to `ttyfix` breaking `gdb`.
We now:
1. Check if first argument (command to execute) is a valid shell and set `SHELL` accordingly
2. If not, check user default shell. Be it a valid shell, we use it
3. Unset `SHELL` otherwise
Review:
https://jetbrains.team/p/ij/reviews/118965/timeline
GitOrigin-RevId: 425b6886b4b48e29f653413c62326afa8033c694
The problem:
https://github.com/microsoft/WSL/issues/10701
When stdout/err are redirected, WSL reports tty size as 1x1 which breaks `ps` tool (famous "expect trouble" message) that some people might have in profile.
`ttyfix` explicitly sets tty size and inserted by `WslDistribution`.
Tiny refactoring moved `getToolPath` to reuse it
Merge-request: KT-MR-12821
Merged-by: Ilya Kazakevich <ilya.kazakevich@jetbrains.com>
GitOrigin-RevId: f33a906b139d22ecdaf0f1b0616ecaaf7bebdd16
fixup! PY-59608: Support ``wslproxy`` when routing is broken by VPN.
When user runs VPN with default gateway pointing to the VPN server and configures interface weight, we can't connect to WSL using its egress IP (traffic to ``172.0.0.0/8`` goes to VPN instead of WSL).
With ``wsl.proxy.connect.localhost`` enabled in registry we bind ``wslproxy`` to ``127.0.0.1`` which could be used in latest WSL2 to connect from Windows to Linux. It is a little bit slow, but still works.
fixup! PY-59608: Support ``wslproxy`` when routing is broken by VPN.
PY-59608: Support ``wslproxy`` when routing is broken by VPN.
When user runs VPN with default gateway pointing to the VPN server and configures interface weight, we can't connect to WSL using its egress IP (traffic to ``172.0.0.0/8`` goes to VPN instead of WSL).
With ``wsl.proxy.connect.localhost`` enabled in registry we bind ``wslproxy`` to ``127.0.0.1`` which could be used in latest WSL2 to connect from Windows to Linux. It is a little bit slow, but still works.
Co-authored-by: Vladimir Lagunov <vladimir.lagunov@jetbrains.com>
Merge-request: IJ-MR-105285
Merged-by: Ilya Kazakevich <ilya.kazakevich@jetbrains.com>
GitOrigin-RevId: 74b5ad4df9c5e95ca4ef53a465f07855a92aa324
Currently, filters support only includes and excludes of files matching the regex patterns. But it should be fairly easy to extend this with other types of filters in the future.
Reviewed-by: IJ-CR-102814
GitOrigin-RevId: 80b7e33aa4d6f89b8a9279d4aa2648783e363bf4
``ifaddrs->ifa_addr`` may be NULL according to ``getifaddr(3)``.
This is a case for the tailscale VPN at least
GitOrigin-RevId: 134cd2bcf03a01b6c52536e23b86a1135450d67b
