Doesn't work when trying to acquire a lease with Azure function core tool

Hi there,

I have an Azure durable function running locally through Azure core function tools. The main entry function is running fine, but it has problem of triggering a orchestration function through orchestration client. From the container log, I can see requests to PUT /devstoreaccount1/myfunc-leases/default/myfunc-control-00?comp=lease failed with 400 error. It seems to have problem with x-ms-proposed-lease-id.

Is there anyway I can see the full request in log?

I have no problem of running this against a real storage account.

[kylepope]

@XiaoningLiu Thanks for the response – that’s news to me but good to hear! Just curious – any clues what a ballpark timeline on a preliminary implementation of the new architecture? The whole lease handing described in the docs is definitely complicated so I’m sure it’ll take time to get that right.

A few more details on things I looked into with my use-case described above:

• I believe MD5 hash error is due to the fact that the GetBlob implementation will calculate the hash from the the raw blob from disk to the response body. I thought I might be able to remove new lease properties I added to the persisted blob prior to hash generation (and add them to response headers instead for example), but I think this would require a bigger change and I’m not sure what the ramifications might be.
• I was specifically looking in general in the code for how some pieces of blob data are converted from raw blob properties to response headers, like lease state (which should be a “x-ms-lease-state” header in a get blob response), but it looks like we’re not doing that in a general way right now.
• I also tried to adding a function to lib/core/env.js to generate a new ID for lease information to perhaps store that separately (e.g. prefix with a “D” character, following what was done for block ID and snapshot ID) and then making the assignment to request.id specifically for lease operations. However, this doesn’t end up working because some of that information needs to be saved as part of the blob I think (I ran into more different errors). I’m sure I’d need to make changes to other pieces of the implementation, but I’d need to figure out which.

Anyway, I’m pretty much out of free cycles at the moment. That said, I’d love to hear more about your future plans.

[XiaoningLiu]

@kylepope thanks for the detailed investigation. Sorry for the late response, I’m quite busy these weeks.

We are working on a new architecture of Azurite, lease is an important part in the implementation. For current Azurite implementation, @edwin-huber any quick thoughs?