search

graalvm / vscode-extensions

Universal Permissive License v1.0
31 stars 8 forks source link

cwd default overridden by executable #20

Closed nirvdrum closed 1 year ago

nirvdrum commented 1 year ago

I'm running into an issue with the GraalVM debugger not running in the correct directory. Without having the cwd set correctly, none of the project files (e.g., Rakefile or Gemfile) can be found by the executing process.

I haven't debugged the extension yet, so I'm not entirely sure what's going on, but if I do not specify the cwd property in my debug configuration, then the working directory is set to the directory that contains the ruby process. If I add an entry like "cwd": "${workspaceFolder}", then everything works as I expect. But, that's the documented default value so I assume something in the extension is overriding the value somewhere.

entlicher commented 1 year ago

This is fixed by https://github.com/graalvm/vscode-extensions/commit/e1d627805538926b42971efc002809418a6e2964 The workspaceFolder is the default now. A new version of GraalVM extension 0.5.25 was released today, which contains this fix.