Debugger: Does not understand environment variables.

[IronicUsername]

Summary

Add environment variable support in debug.json files.

Description

Steps to trigger the problem:
0. (OPTIONAL) have direnv installed and launch zed with it running prior (just to make sure it sources the envs)

1. Configure Golang language support as described here
2. Go into a Go Project, add the .zed/debug.json and add this:

[
{
  "label": "Remote Debug",
  "adapter": "Delve",
  "request": "attach",
  "mode": "remote",
  "tcp_connection": {
    // "host": "192.168.122.149",  <-- This works
    "host": "${REMOTE_HOST}",  <-- but i want it like this (doesnt work)
    "port": 12080
  }
}
]

3. Start debugging (F4 by default)
4. ???
5. NO PROFIT!

Expected Behavior:
Zed should understand the REMOTE_HOST env variable

Actual Behavior:
It says this:

String does not match the pattern of "^((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}$".

Zed Version and System Specs

Zed: v0.191.3 (Zed Preview)
OS: Linux X11 arch unknown
Memory: 30.9 GiB
Architecture: x86_64
GPU: NVIDIA GeForce RTX 4060 || NVIDIA || 575.57.08

[IronicUsername]

It would be best if it is possible to pass in env vars and zed "somehow" understands them and also can evaluate their contents...

[IronicUsername]

as reference here my vscode debug-launch config which i've been using the last 2 years:

...
  "launch": {
    "version": "0.2.0",
    "configurations": [
      {
        "name": "Remote Debug",
        "type": "go",
        "request": "attach",
        "mode": "remote",
        "port": 12080,
        "host": "${env:REMOTE_HOST}"
        // "trace": "verbose",  // uncomment to see verbose output
      }
    ]
  }

[jansol]

It would be best if it is possible to pass in env vars and zed "somehow" understands them and also can evaluate their contents...

That requires you to launch zed from an environment that has those variables set (and it has to be the first instance you launch since others would just attach to the existing one).

That said if you have a .env that sets environment variables, zed does already pick that up (for some purposes at least, not sure if it interacts with debugging yet).

[IronicUsername]

That requires you to launch zed from an environment that has those variables set (and it has to be the first instance you launch since others would just attach to the existing one).

i am already doing this.

not sure if it interacts with debugging yet

well i'm almost certain it does not and if so then the fix for this would be pretty easy since the actual problem is that the validation for the tcp_connetion.host value must consist out of numbers.

inside the .zed/debug.json

An env variable can not be just numbers.. or i mean it can but thats just unpractical and it is wrong to assume in this case that the devs "want you to use numerical env-vars"

Since the validation of the field does not work, the debugger therefore also does not work.. not sure if this is wanted behavior but this is what is currently going on.

So imo:

• rm validation (or at least allow also string-input) on the host / port / timeout fileds (since all of them can be variable
  OR
• make it so that even-tho it throws the regex-warning but still lets me debug

i have a bias towards the first option.