Michael B. McCoy

Thanks, and apologies for the slow response. This works when my laptop goes to sleep, which covers 95% of the my use case. (WiFi power cycling still triggers the issue,...

Hmm.... I don't think that's the source of the problem. In particular, when I use `ssh` from the command line (using the same user/host that I use in VSC), I...

I'm not able to trigger the issue right now, but `$SSH_AUTH_SOCK` was definitely set, and it looked structurally correct, like `/tmp/ssh-cT3h6tFlau/agent.316`, only the directory (and file) didn't exist.

Ok, I'm able to reproduce now. These are all run from within the VSCode terminal. Here's the initial situation: ```bash $ echo $SSH_AUTH_SOCK /tmp/ssh-7G9TqKKzBp/agent.30503 $ ls -la /tmp/ssh*/** srwxr-xr-x 1...

Here's the output for a run where I just had this issue: https://gist.github.com/mbmccoy/331ba3674877b7c8769b482f78e467b7 Note that it does seem to have the correct agent in the logs (`/tmp/ssh-vA5Po49GCF/agent.28474`), but it was...

I suppose I dropped the ball on getting back to you on this. No, I don't have any settings that are related to the terminal or remote set in my...

Was able to trigger this just now. ~It may be related to the fact that I also connect (and forward my agent) from another terminal.~ (see note below) Here's the...

One use case that I stumbled on today is mounting `/var/run/docker.sock` to allow the container to access a docker API without setting up a true "docker in docker" situation. My...

I'm having a similar problem. It's related to this issue: https://github.com/protocolbuffers/protobuf/issues/9730 The issue seems to stem from the fact that 3.20.0 `protoc` does in fact _not directly define_ the classes...

I've got another use case for graceful shutdown of `test` targets in particular. I stand up database fixtures using docker containers during test runs (using `pytest`). Under normal circumstances, these...