Open glotchimo opened 1 year ago
Can confirm the same behavior. Is the dlv path hardcoded in this plugin somewhere?
Update: I did check for updates
on the Go-Bee extension, and it prompted me to install dlv.
(Note: I already had dlv installed and working in terminal, so I'm not sure where it installed to)
After that Debug worked. However, it is not respecting my Run pipeline configuration.
I'm trying to execute debug in a subfolder with:
dlv debug structs/main.go
But it always start debug in the workspace folder.
Update 2: Got it to work by specifying Go Debug > Program as structs/main.go
.
Thanks @halfnibble! I ran into the same issue and was able to fix it by checking for updates and installing dlv
via the prompt.
We don't know how to find dlv in your environment. Possibly we should fix that. But certainly using the plugin to install its own version will work, as you've learned.
I get a
The file "dlv" does not exist
when trying to run the debugger. I've tried with default settings on a fresh install, and with two different verifieddlv
binary paths, specifying bothDelve (Auto)
andCustom
options for good measure. I've also made sure to check both linked paths and direct paths. The binaries work, as I can use them without issue from the terminal. The only additional information in the report is as follows:This has occurred on both macOS 13 and 14 on two different machines (M1 Pro, M2 Pro, respectively; latest build of Nova and a development build).
Edit: using Go-Bee v0.8.0 (looks like a related issue was patched in v0.7.0).