Asher

Yeah that is pretty much what I was thinking, a file that is either a socket or a pipe but then you would have to do things like `echo test...

Nice! That `ENOENT` usually means VS Code is still compiling (really bad error, we should fix it). Once you see something like ``` [Code OSS] [watch-client ] [14:40:53] Finished compilation...

Awesome!!!

Does this for sure not reproduce for you in Codespaces? I tried but it reproduces for me in Codespaces. If so we might want to raise it upstream to VS...

I marked this as upstream. I see they mentioned not restoring state is expected behavior, but it seems like it is not expected that the debugging process should stay up...

Hard to say what the problem is without seeing the source code for your program but perhaps it needs some mechanism for waiting until the input has been fully received...

Is there any way I can reproduce this locally? Here is what I did: 1. Install and launch minikube. 2. minikube addons enable ingress (not sure this was necessary). 3....

Ah yup, we have ran into this ourselves before (and with many others in `lib/vscode/extensions`). Your analysis is spot-on; that is indeed a false positive. Adding this to the docs...

The best we can do as far as work in this repo is to document in `SECURITY.md` that anything in the format `lib/vscode/extensions/$name/package.json` is a false positive. Unless Trivy becomes...

Oh also I just found https://github.com/aquasecurity/trivy/discussions/6112