No drag and drop foldername to terminal available

[martinw-intersport]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.100.3
• OS Version: Windows 11 Pro 24H2

Steps to Reproduce:

1. Connected to DevContainer and clone repo inside it
2. Open explorer and drag one folder into terminal, and folder path is not dropped into terminal (this function works previously)

[meganrogge]

any errors in the dev tools console?

[meganrogge]

If this is a confirmed regression, it would help to know which change caused it. We maintain a node.js based CLI tool vscode-bisect that automatically downloads and runs previous VS Code insiders and asks for each build if the issue reproduces. It takes up to 8 steps to find exactly the build that caused the regression.

Steps:

• install node.js (if not yet done)
• npx --yes @vscode/vscode-bisect@latest
• follow the instructions until you found the offending build (its fine to leave the commit empty)
• report back the commit range in this issue

Thanks!

[martinw-intersport]

HI @meganrogge

any errors in the dev tools console?

There's no error in terminal and output, and darg and drop works for file but not for folder.

And I got following error inside node container starting from windows powershell, seems vsc insider cannot be started.

/ # npx --yes @vscode/vscode-bisect@latest
✔ Commit or version of released insiders build that reproduces the issue (leave empty to pick the latest build) … 138f619c86f1199955d53b4166bef66ef252935c
✔ Commit or version of released insiders build that does not reproduce the issue (leave empty to pick the oldest build) …
[build] fetching all builds from https://update.code.visualstudio.com/api/commits/insider/linux-x64?released=false...
[build] fetching all builds from https://update.code.visualstudio.com/api/commits/insider/linux-x64?released=true...
[build] total 30 builds with roughly 5 steps
[build] starting desktop build 2aceb1d827febabfed0627db9c72d747d98a3200...
? Is 2aceb1d827febabfed0627db9c72d747d98a3200 good or bad? › - Use arrow-keys. Return to submit.
❯   Good
    Bad
    Retry
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: spawn /tmp/vscode-bisect/.builds/2aceb1d827febabfed0627db9c72d747d98a3200/VSCode-linux-x64/code-insiders ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn /tmp/vscode-bisect/.builds/2aceb1d827febabfed0627db9c72d747d98a3200/VSCode-linux-x64/code-insiders',
  path: '/tmp/vscode-bisect/.builds/2aceb1d827febabfed0627db9c72d747d98a3200/VSCode-linux-x64/code-insiders',
  spawnargs: [
    '--accept-server-license-terms',
    '--extensions-dir',
    '/tmp/vscode-bisect/.data/extensions',
    '--skip-release-notes',
    '--disable-updates',
    '--user-data-dir',
    '/tmp/vscode-bisect/.data/data',
    '--no-cached-data',
    '--disable-telemetry'
  ]
}

Node.js v22.16.0

[meganrogge]

@joshspicer can you repro? any idea why insider's wouldn't open in a container?

[vs-code-engineering]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!