Debugger: Not sure why environment variables are not getting set

[dipankardas011]

Summary

Environment variables set in the debug config for Go programing not working as expected

Description

Steps to trigger the problem:

1. I had specified in the $PROJECT/.zed/debug.json

[
  {
    "label": "Program cloudmeta",
    "adapter": "Delve",
    "program": "cmd/app.go",
    "request": "launch",
    "mode": "debug",
    "args": ["-run", "cluster.meta.refresh"],
    "env": {
      "KSCTL_ENVIRONMENT": "prod",
    }
  }
]

2. then in my go program I ran os.Environ()
3. There I couldn't see Any env with Prefix as KSCTL_

Expected Behavior:
Actual Behavior:

Zed Version and System Specs

Zed: v0.191.4 (Zed)
OS: Linux Wayland fedora 41
Memory: 15.3 GiB
Architecture: x86_64
GPU: Intel(R) Iris(R) Plus Graphics (ICL GT2) || Intel open-source Mesa driver || Mesa 25.0.7

[cole-miller]

Thanks for the report. I tried to reproduce this as follows:

• Put this in cmd/app.go

import "os"
import "fmt"

func main() {
    fmt.Println(os.Environ())
}

• Put the scenario you specified into .zed/debug.json
• Run that scenario from the list in the new process modal (F4)

With that I do see KSCTL_ENVIRONMENT=prod in the printed environment.

Are you able to share a debug scenario and/or project that's closer to the real use-case where you're seeing this?

[dipankardas011]

Yes now its working, anyways closing the issue
There was a update may be that fixed it

[dipankardas011]

Also is there way to tell zed debugger to use .env file instead of specifying it in config?

[cole-miller]

@dipankardas011 we don't support envFile in debug configurations right now but we'd like to add support for it at some point!