-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnixProcessProvider Failed to Find Dapr Process CMD on Mac #169
Comments
sk593
added a commit
to sk593/vscode-dapr
that referenced
this issue
Jun 18, 2021
sk593
added a commit
to sk593/vscode-dapr
that referenced
this issue
Jul 1, 2021
sk593
added a commit
to sk593/vscode-dapr
that referenced
this issue
Jul 6, 2021
…dapr into daprdProcBug-microsoft#169 merging main into branch
sk593
added a commit
to sk593/vscode-dapr
that referenced
this issue
Jul 13, 2021
sk593
added a commit
that referenced
this issue
Jul 15, 2021
* updated process finder to get all daprd instances * removed added functions from app provider * updated processProvider to look for all forms of daprd (daprd and ~/daprd) * removed unneeded code from daprAppProvider * updated to use which module to find daprd executables * expanded mac proc finder logic * updating package-lock * added open telemetry module * minor changes to process provider logic * minor refactoring/changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The current implementation for finding Dapr processes uses the library ps-list, the usage can be found here:
vscode-dapr/src/services/processProvider.ts
Line 23 in 665dabf
There's a method for Windows and Mac, however on Mac there's been a bug were the current Dapr applications have trouble being found. It seems that the current processes cmd name matching relied on 'daprd' but simply changing the name to 'dapr' as the matching string allowed for dapr cli initiated apps to be found.
** Tests **
Tested locally with running the following Dapr apps,
dapr run --app-id pppptest --app-port 3560 --dapr-http-port 3850 node app.js
dapr run --app-id nodeapptesttt --app-port 3550 --dapr-http-port 3800 node app.js
The text was updated successfully, but these errors were encountered: