Skip to content

copilot-debug generating unusable configuration for Ruby #3736

@tomdracz

Description

@tomdracz
  • Copilot Chat Extension Version: 0.23.2
  • VS Code Version: 1.96.2
  • OS Version: MacOS 14.7.2

Using copilot-debug command with Ruby generates a configuration that's not able to be used with non-deprecated debugger extensions.

Steps to Reproduce:

  1. copilot-debug --print bundle exec rails s
  2. Configuration generated as:
    {
      "type": "ruby",
      "request": "launch",
      "name": "Launch Rails Server",
      "program": "${workspaceFolder}/bin/rails",
      "args": [
        "s"
      ],
      "useBundler": true
    }
  1. Image

  2. Running just copilot-debug bundle exec rails s warns We generated a "ruby" debug configuration, but you don't have an extension installed for that. Do you want to look for one?. Searching for extensions brings up deprecated ruby extension as first result.
    Image

  3. The generated launch configuration can be made to work with few tweaks, mainly using "type": "ruby_lsp" with associated ruby-lsp extension.

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions