[Bug]: Reopen in Devbox shell doesn't work

[mikenikles]

Current Behavior (bug)
I use Cursor (cursor.sh) as my editor (update: I have the same issue with VS Code), with the Devbox extension installed. When I use the "Devbox: Reopen in Devbox shell environment" command, Cursor closes, but doesn't reopen again.

Expected Behavior (fix)
Cursor closes and reopens.

Additional context

devbox version -v

devbox version -v
Version:     0.8.1
Platform:    darwin_arm64
Commit:      a0bdff918b3dde5ebcfc488f72df5efdf3426253
Commit Time: 2023-11-07T21:43:27Z
Go Version:  go1.21.3
Launcher:    0.2.0

devbox.json

{
  "packages": [
    "rustup@latest",
    "libiconv@latest"
  ],
  "env": {
    "PROJECT_DIR": "$PWD"
  },
  "shell": {
    "init_hook": [
      "rustup default stable"
    ],
    "scripts": {
      "test": [
        "echo \"Error: no test specified\" && exit 1"
      ]
    }
  }
}

[mikenikles]

I tried that command in VS Code Insider and VS Code, but it didn't work there either. Both editors are on their latest versions.

[Lagoja]

@mikenikles Can you share what OS you are encountering this issue on? We've seen some issues with macOS Sonoma, but haven't found a reliable repro

[mikenikles]

I recently upgraded to Sonoma 14.1.1, but I also saw it on whichever the previous OS version was. Now that I'm on Sonoma though and given it's a known issue, I'll accept that it doesn't work :)

[aacebedo]

I have the same problem on NixOS 23.11

[mohsenari]

@mikenikles @aacebedo We just released version 0.1.4 of the extension. It adds a setting called "Debug Mode" that if you enable, it will keep a log of events for "Reopen in Devbox Shell" feature. The log file is in ./devbox/extension.log. If your problem is still persisting, update the extension and enable debug mode and send me the content of this log file. This will help troubleshooting the issue significantly.

[mohsenari]

for reference:

[aacebedo]

@mikenikles @aacebedo We just released version 0.1.4 of the extension. It adds a setting called "Debug Mode" that if you enable, it will keep a log of events for "Reopen in Devbox Shell" feature. The log file is in ./devbox/extension.log. If your problem is still persisting, update the extension and enable debug mode and send me the content of this log file. This will help troubleshooting the issue significantly.

Go this on code-insiders 1.86 and devbox 0.8.2 on NixOS, not sure it is very useful:

[Tue, 30 Jan 2024 13:58:14 GMT] Installing devbox packages
[Tue, 30 Jan 2024 13:58:14 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 13:58:14 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 13:58:14 GMT] child process closed with exit code: 1
[Tue, 30 Jan 2024 14:44:11 GMT] Installing devbox packages
[Tue, 30 Jan 2024 14:44:11 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 14:44:11 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 14:44:11 GMT] child process closed with exit code: 1
[Tue, 30 Jan 2024 16:19:59 GMT] Installing devbox packages
[Tue, 30 Jan 2024 16:19:59 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 16:19:59 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 16:19:59 GMT] child process closed with exit code: 1

[mikenikles]

I see the same output.

I also see the following when I select the Output tab, then "Extension Host":

2024-01-30 14:28:51.824 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-ssh, startup: false, activationEvent: 'onStartupFinished', root cause: jetpack-io.devbox
2024-01-30 14:28:51.867 [info] ExtensionService#_doActivateExtension jetpack-io.devbox, startup: false, activationEvent: 'onStartupFinished'
2024-01-30 14:28:51.878 [info] ExtensionService#_doActivateExtension ms-vscode.remote-explorer, startup: false, activationEvent: 'onCommand:remote-internal.setActiveFolders'
2024-01-30 14:29:16.560 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-01-30 14:29:56.720 [error] undefined devbox.reopen {"value":"jetpack-io.devbox","_lower":"jetpack-io.devbox"}

[aacebedo]

I see the same output.

I also see the following when I select the Output tab, then "Extension Host":

2024-01-30 14:28:51.824 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-ssh, startup: false, activationEvent: 'onStartupFinished', root cause: jetpack-io.devbox
2024-01-30 14:28:51.867 [info] ExtensionService#_doActivateExtension jetpack-io.devbox, startup: false, activationEvent: 'onStartupFinished'
2024-01-30 14:28:51.878 [info] ExtensionService#_doActivateExtension ms-vscode.remote-explorer, startup: false, activationEvent: 'onCommand:remote-internal.setActiveFolders'
2024-01-30 14:29:16.560 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-01-30 14:29:56.720 [error] undefined devbox.reopen {"value":"jetpack-io.devbox","_lower":"jetpack-io.devbox"}

@mikenikles On nixos ?

@mohsenari dld you check the extension on insiders build ?

[mikenikles]

I use Mac OS Sonoma

[mohsenari]

@aacebedo @mikenikles the changes I made to enable debug logs relied on a feature in devbox cli that wasn't released yet (my apologies). We now have released devbox version 0.9.0. Would you please update your devbox to newest version and retry this?