Azure / logicapps

Azure Logic Apps labs, samples, and tools
MIT License
363 stars 301 forks source link

Debugger won't start if default terminal is set to WSL #914

Closed RussSmi closed 8 months ago

RussSmi commented 10 months ago

Describe the Bug

The logic app debugger will not launch if the default terminal is set to WSL. Recently, without any changes to my VS Code settings, logic app debugging stopped working, it gives the following error:

image

Hopefully it is clear in the image. You can see that it is trying to execute: "C:\WINDOWS\System32\wsl.exe -d Ubuntu -e func host start" terminated with exit code: 1. Why, when I am working in windows, does run WSL when I hit F5? The answer it seems is because that is the default terminal. This is a change in behaviour, it did not do this 2 weeks ago.

Plan Type

Standard

Steps to Reproduce the Bug or Issue

Open VS Code in Windows Set default terminal to WSL Create a new logic app project, accept all defaults Add an http request trigger Add an http response and return the text "Hello World" Select 'Start Debugging' from the run menu

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "Response": {
                "type": "Response",
                "kind": "Http",
                "inputs": {
                    "statusCode": 200,
                    "body": "Hello World"
                },
                "runAfter": {}
            }
        },
        "contentVersion": "1.0.0.0",
        "outputs": {},
        "triggers": {
            "When_a_HTTP_request_is_received": {
                "type": "Request",
                "kind": "Http"
            }
        }
    },
    "kind": "Stateful"
}

Screenshots or Videos

No response

Additional context

image

AB#25847875

github-actions[bot] commented 9 months ago

This issue is stale because it has been open for 45 days with no activity.

github-actions[bot] commented 8 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.