You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into an issue when attempting to activate a flox environment on a remote Linux machine while using VS Code's Remote SSH feature. I can activate the flox environment within a terminal, and I am using Flox on my local machine (macOS) for a different project. But it seems that this particular combination doesn't work out. As soon as I click 'Activate and environment' in the Flox extension, the whole VS Code window closes (as it does when activating locally), but then never re-opens. I'm not entirely sure if it's a crash or just a shutdown.
System Info
Machine with human: MacBook Pro M3 Max on macOS 15.3.1 (24D70)
Machine with Flox environment: Some random Fedora Linux machine
Happy to share any more info if it's helpful!
The text was updated successfully, but these errors were encountered:
@parrotmac I also ran into this and asked the devs and it was confirmed that it is a known issue/intentional that it only runs locally for now. This would be a huge use case for me, and the major reason I end up not using a vscode based editor for now.
Hi!
I'm running into an issue when attempting to activate a flox environment on a remote Linux machine while using VS Code's Remote SSH feature. I can activate the flox environment within a terminal, and I am using Flox on my local machine (macOS) for a different project. But it seems that this particular combination doesn't work out. As soon as I click 'Activate and environment' in the Flox extension, the whole VS Code window closes (as it does when activating locally), but then never re-opens. I'm not entirely sure if it's a crash or just a shutdown.
System Info
Machine with human: MacBook Pro M3 Max on macOS 15.3.1 (24D70)
Machine with Flox environment: Some random Fedora Linux machine
Happy to share any more info if it's helpful!
The text was updated successfully, but these errors were encountered: