VSCode extension: Devbox: Reopen in Devbox Shell Environment fails to re-open VSCode

[PaulBurridge]

What happened?

Hi,

Using the VSCode extension version 0.1.5

"Devbox: Reopen in Devbox Shell Environment" closes window but fails to open a new one.

This is when connected to a Debian WSL environment inside a directory containing a devbox.json file

Main WSL environment has a global devbox config enabled via .zshrc

Thanks in advance for any assistance.

Steps to reproduce

1. Open VSCode, connect to WSL and open a directory containing a devbox.json file.
2. Press ctrl+p, select "Devbox: Reopen in Devbox Shell Environment"
3. VSCode closes window but fails to reopen a new one

Note main WSL environment has a global devbox config enabled via .zshrc

Command

No response

devbox.json

{
  "$schema":  "https://raw.githubusercontent.com/jetify-com/devbox/0.12.0/.schema/devbox.schema.json",
  "packages": ["libuuid@latest"],
  "shell": {
    "init_hook": [
      "echo 'Welcome to devbox!' > /dev/null"
    ],
    "scripts": {
      "test": [
        "echo \"Error: no test specified\" && exit 1"
      ]
    }
  }
}

Devbox version

0.12.0

Nix version

nix (Nix) 2.21.2

What system does this bug occur on?

Linux (x86-64)

Debug logs

Using "devbox.enableDebugMode": true

Contents of /home/pab/projects/gbr-tms2-portal/.devbox/extension.log:

[Mon, 08 Jul 2024 08:54:46 GMT] Installing devbox packages
[Mon, 08 Jul 2024 08:54:46 GMT] Updating VSCode configurations
[Mon, 08 Jul 2024 08:54:46 GMT] Calling "devbox integrate" to setup environment
[Mon, 08 Jul 2024 08:54:46 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Mon, 08 Jul 2024 08:54:46 UTC] Computing devbox environment
[Mon, 08 Jul 2024 08:54:46 UTC] Signaling VSCode to close
[Mon, 08 Jul 2024 08:54:46 UTC] Re-opening VSCode in computed devbox environment
[Mon, 08 Jul 2024 08:54:46 UTC] stdout:  
 stderr: Unable to connect to VS Code server: Error in request.
Error: connect ECONNREFUSED /run/user/1000/vscode-ipc-79a8ab0f-dd46-4a23-aa1e-6bfd4788a48a.sock
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '/run/user/1000/vscode-ipc-79a8ab0f-dd46-4a23-aa1e-6bfd4788a48a.sock'
}

Permissions:

stat /run/user/1000/vscode-ipc-79a8ab0f-dd46-4a23-aa1e-6bfd4788a48a.sock
  File: /run/user/1000/vscode-ipc-79a8ab0f-dd46-4a23-aa1e-6bfd4788a48a.sock
  Size: 0               Blocks: 0          IO Block: 4096   socket
Device: 0,75    Inode: 36          Links: 1
Access: (0755/srwxr-xr-x)  Uid: ( 1000/     pab)   Gid: ( 1000/     pab)
Access: 2024-07-08 09:53:07.963234932 +0100
Modify: 2024-07-08 09:53:07.963234932 +0100
Change: 2024-07-08 09:53:07.963234932 +0100
 Birth: -

[apgrucza]

Looks the same as #1319