[Bug]: Reopen in Devbox shell doesn't work #1619
Comments
|
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. |
mikenikles
changed the title
|
@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 |
|
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 :) |
|
I have the same problem on NixOS 23.11 |
|
@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 |
|
for reference:
|
Go this on code-insiders 1.86 and devbox 0.8.2 on NixOS, not sure it is very useful: |
|
I see the same output. I also see the following when I select the Output tab, then "Extension Host": |
@mikenikles On nixos ? @mohsenari dld you check the extension on insiders build ? |
|
I use Mac OS Sonoma |
|
@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? |
|
With devbox 0.9.0: That makes sense since Cursor doesn't have a I'll have to look into it in more detail later, but posting this for now in case anyone has ideas. |
|
Fixed it with However, it gets weirder now 😕: Possibly no longer Devbox related 🤔?! |
|
If I add an empty Cursor closes the current window and stays like that – no open window. |
|
@mikenikles When you see this line in the log: |
|
Excellent!! That does the trick, I'm all set. Thank you 🙏! Funny enough, running that "Shell Command: Install 'Code' command" does the following: Looks like my symlink pointed to the wrong file :) Leaving this open until @aacebedo confirmed it works for him too. |
|
I saw the same issue because the binary for the insiders build is |
|
@aacebedo that's a good suggestion. I can add in settings the path to binary that opens vscode so that it can be configurable. |
|
@mohsenari I'm experiencing a similar (or identical?) error. Host is Windows target is an Ubuntu 20.04 VM connected via SSH remote. When executing "Devbox: Reopen in Devbox shell environment", the following error is displayed.
The contents of the What error log (as mentioned in the error dialog) is relevant here to pin the error? Digged a bit into the source code. I suspect the error occurs at line 98 in
|
|
@tmeckel the functionality of |
|
@mohsenari sadly to say, then devbox is not an option for me. Stick to DevContainers then. |
|
@mohsenari does this might change anything? I know they're talking about connecting to a WSL instance when you're connected to a Windows machine via SSH. But I think they might have changed the inner workings of WSL remote support for that. |
|
@tmeckel I need to do some testing to see if there is a way to connect to WSL from VSCode's extension. Then spawn a subprocess, compute devbox env and lastly, reopen vscode from within WSL instance. |
|
Can't wait about your results 👍🏼👍🏼 would be awesome to be able to use devbox in WSL |
|
It would be amazing if at the same time it could be resolved on remove servers as well. as mentioned here: #1781 (comment) |
…vscodium (#2309) ## Summary Title plus, removed remote-ssh dependency to allow publishing the extension in open-vsx marketplace. Addresses #1619 I've been wanting to get this fixed for a while but with recent traction on vscode alternatives it makes sense to finally get this fix in. ## How was it tested? steps: 1. compile devbox binary (devbox run build) 2. update line 56 in `vscode-extension/src/devbox.ts` to the absolute path to compiled devbox binary 3. have all 3 of cursor, vscodium and vscode installed 4. have `vsce` installed globally (npm install -g vsce) 5. in devbox/vscode-extension folder run: `vsce package && code --install-extension devbox-0.1.6.vsix && cursor --install-extension devbox-0.1.6.vsix && codium --install-extension devbox-0.1.6.vsix` 6. quit any already open code editor, open it to refresh the editor with new installed extension 7. cmd + shift + p and type `devbox: reopen in devbox` and hit enter in vscode, cursor, and vscodium
|
@mikenikles vscode extension version 0.1.6 was published. With this version, reopen in devbox should work fine with Cursor. Closing this issue but reopen if the issue is not resolved. |
|
@mohsenari still no luck with a devbox environment located on remote VM using SSH. Debug log is not very helpful |
|
Work around on remote environments: |
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 -vdevbox.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" ] } } }The text was updated successfully, but these errors were encountered: