Skip to content
This repository was archived by the owner on Jun 24, 2025. It is now read-only.
This repository was archived by the owner on Jun 24, 2025. It is now read-only.

Debugger Spawn Error #312

Description

@PShipstone

Does this occur consistently? Yes
Repro steps:

  1. Clicking on debug when application is ran from terminal (or with the dapr.yaml Start Run menu option) using dapr run -f . to run the dapr.yaml file. This means I cannot attach the debugger within VSCode.

image

image

image

Action: vscode-dapr.applications.debug
Error type: ENOENT
Error Message: spawn c:\Users\redacted:username.vscode\extensions\ms-azuretools.vscode-daprredacted:id\dist\vendor\fastlistredacted:idx64.exe ENOENT

In case anybody else experiences this problem, it is possible to debug the app within Visual Studio 2022 by attaching to process (debug > attach to process...):

image

Version: 0.8.0
OS: win32
OS Release: 10.0.22631
Product: Visual Studio Code
Product Version: 1.84.2
Language: en

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions