Failed to debug second time if using Azurite

[ejizba]

Repro steps:

1. Create a javascript project
2. Add a timer trigger
3. Set AzureWebJobsStorage to UseDevelopmentStorage=true
4. Make sure azurite is running (https://github.com/Azure/Azurite/blob/master/README.md#installation-and-usage)
5. Debug
6. Detach
7. Debug again

Expected:
It attaches

Actual:
It never attaches because the following is never printed:

Host lock lease acquired by instance ID '000000000000000000000000D21F4D53'.

[ejizba]

Azure/Azurite#37

[JustinGrote]

This happens if you use any remote storage in my observation, it never hits the lease request message so it never backgrounds. To fix, the problemMatcher for the task should match on the Job host starting, not on the lease request.

[5/3/2019 1:02:23 AM] Host initialized (632ms)
[5/3/2019 1:02:23 AM] Host started (644ms)
[5/3/2019 1:02:23 AM] Job host started

EDIT:

For a temporary fix, change your tasks.json for func start to this to override the background job matching lines. Worked for the powershell worker at least.

        {
            "type": "func",
            "command": "host start",
            "problemMatcher": {
                "base": "$func-watch",
                "background": {
                    "activeOnStart": true,
                    "beginsPattern": "^Azure Functions Core Tools|Restarting host$",
                    "endsPattern": "Job host start"
                }
            },
            "isBackground": true,
            "presentation": {
                "group": "azfunc"
            }
        }

[ejizba]

@JustinGrote we used to do that, but it doesn't work in all cases. See #660

Azurite specifically does not work as described in the above issue. If you're not seeing Host lock lease acquired by instance ID in a remote case, please file a separate issue with repro steps, project language, etc. and we can look into it.

[ejizba]

Seems like both messages (Job host start and Host lock lease acquired) are not ideal, so I filed an issue on the func cli: Azure/azure-functions-host#4384

[JustinGrote]

I ended up just going back to Azure Storage Explorer due to a lot of issues beyond that. Hopefully it gets working but for cross-plat development I just point it to a "real" queue in my dev subscription for now as a workaround.

…

On Fri, May 3, 2019 at 11:06 AM Eric Jizba ***@***.***> wrote: Seems like both messages (Job host start and Host lock lease acquired) are not ideal, so I filed an issue on the func cli: Azure/azure-functions-host#4384 <Azure/azure-functions-host#4384> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1245 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADUNKUUVMH2BYGCC6AKIJW3PTR5JZANCNFSM4HJP7SUA> .

[ejizba]

I tried the latest version of Azurite and this seems to be working now