Can't activate environments

[apenney]

I have recently switched to a new machine, and I'm running Linux. After installing nix and then flox to the global profile I am unable to get the vscode extension to work at all, and I don't know what else to troubleshoot.

Flox is working fine from a terminal:

○ whereis flox
flox: /nix/store/bcwfhn5ng78vpc6h9j0gdyf3gnymfn1y-flox-1.7.6-g83a54b5/bin/flox


◎ flox
flox version 1.7.6-g83a54b5

Usage: flox OPTIONS (init|activate|search|install|...) [--help]

Use 'flox --help' for full list of commands and more information

No active environments. Use 'flox envs' to list all environments.

When I launch vscode and try to activate the environment from the extension, I just see this (in the vs code console):

Things I've tried:

• launching with flox activate -- code .
• Deleting everything in .config/Code and starting over
• Trying the pre-release (0.0.2 version)

Via some AI assisted debugging, it seems like at some point it parses flox --envs json and then fails, as this shows up in one of the code logs:

Activating extension flox.flox failed: SyntaxError: Unexpected end of JSON input
    at Env.reload (.../flox.flox-0.0.2/out/env.js:<line>)

When I check flox envs --json | jq (to prove it parses fine) I get:

lox envs --json | jq .
{
  "active": [],
  "inactive": [
    {
      "path": "/home/apenney/code/elixir/heads_up/.flox",
      "pointer": {
        "name": "heads-up",
        "version": 1
      },
      "type": "dot-flox"
    },
    {
      "path": "/home/apenney/flox/elixir/.flox",
      "pointer": {
        "name": "elixir",
        "version": 1
      },
      "type": "dot-flox"
    },
    {
      "path": "/home/apenney/flox/postgres/.flox",
      "pointer": {
        "floxhub_url": "https://hub.flox.dev/",
        "name": "postgres",
        "owner": "flox",
        "version": 1
      },
      "type": "dot-flox"
    }
  ]
}

I don't really know what else to try from a troubleshooting perspective! I'd appreciate any suggestions.

[apenney]

Also in case it helps, chatgpt is convinced the issue is this:

[apenney]

I let codex take a stab at doing the local patching it wanted, and that ... half fixed it. It was able to restart, and it can see postgres is up, but it's still in a half broken state:

I think it was definitely onto something however.

[apenney]

#136 - I made this based on some of the stuff it changed for me locally. I have never written a line of typescript in my life, this was entirely AI driven and purely to demonstrate the issue. I had it write a test, make sure that failed, then it wrote that complex looking parser to handle the various cases.

I wouldn't expect this to be mergable code, but it felt wrong to just leave a couple of screenshots and no easy way to show the issue.

[apenney]

Just pushed more changes that make it actually work end to end. I can now press activate environment and it works. Prior to this the parsing fix just made it attempt to restart code but it would just shut down. Eventually when I got it to start, it still didn't work. This giant set of changes makes it actually work.