Bad behaviour for named pipe (mkfifo)

shoffmeister commented 2 years ago

Issue Type: Bug

The presence of a named pipe (created via mkfifo on Linux) results in undesirable IDE behaviour; on (at least) Linux (possibly also macos)

mkdir x && cd x
mkfifo this-is-a-named-pipe
code .

You now have

Problems:

the pull "doing something" indicator on editor tab never stops ... doing... - IMHO, it should not even attempt doing anything with pipes.
"Unknown File Type" - yeah, it's a named pipe ;)
Trying to delete the pipe from vscode results in the operation never completing

None of that is really breaking, and you'd be right in wondering why I would actually have named pipes in a directory (hierarchy) which vscode touches, but then ...

I think the overall expectation is

don't try to open named pipes
perhaps show "Named Pipe" if you encounter one (find -type p)
make delete work

VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:24.808Z) OS version: Linux x64 5.17.4-200.fc35.x86_64 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2903)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|1, 1, 0| |Memory (System)|31.32GB (20.93GB free)| |Process Argv|. --crash-reporter-id 80e0ae97-0bc4-4a76-8337-f435f2ec1554| |Screen Reader|no| |VM|100%| |DESKTOP_SESSION|/usr/share/xsessions/plasmax11| |XDG_CURRENT_DESKTOP|KDE| |XDG_SESSION_DESKTOP|KDE| |XDG_SESSION_TYPE|x11|

Extensions (20)

Extension|Author (truncated)|Version ---|---|--- project-manager|ale|12.5.0 path-intellisense|chr|2.8.0 xml|Dot|2.5.1 gitlens|eam|12.0.6 vscode-drawio|hed|1.6.4 vscode-peacock|joh|4.0.1 milkdown|mir|0.0.12 vscode-docker|ms-|1.22.0 python|ms-|2022.4.1 vscode-pylance|ms-|2022.4.2 remote-containers|ms-|0.231.6 remote-ssh|ms-|0.78.0 remote-ssh-edit|ms-|0.80.0 vscode-remote-extensionpack|ms-|0.21.0 vscode-commons|red|0.0.6 vscode-xml|red|0.20.0 vscode-yaml|red|1.6.0 code-spell-checker|str|2.1.11 code-spell-checker-german|str|2.0.3 shellcheck|tim|0.19.2

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 pythonvspyl392:30443607 pythontb:30283811 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 pythondataviewer:30285071 vscod805:30301674 pythonvspyt200:30340761 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593:30376534 vsc1dst:30438360 pythonvs932:30410667 wslgetstarted:30449410 pythonvsnew555:30457759 vscscmwlcmt:30465135 cppdebugcf:30475217 ```

joshuahhh commented 9 months ago

FWIW, I just ran into the "Trying to delete the pipe from vscode results in the operation never completing" issue.

mofosyne commented 6 months ago

Not a common problem, but it's something I did hit so I hope this is fixed.

At the very least don't open named pipes. But if possible it be nice to have a mode to inspect the pipe as character streams out of it. Or to push in characters.

E.g. maybe have two panels where you can enable input/output into the pipe. (press to read pipe, press to write to pipe)

microsoft / vscode

Bad behaviour for named pipe (mkfifo) #148034