-
Notifications
You must be signed in to change notification settings - Fork 371
WebJobs Blob Trigger does not work correctly with Storage Emulator #430
Comments
Hi, Isaac -- We'd be interested in viewing your emulator logs and Fiddler traces. |
@kfarmer-msft where can I can the logs from? |
Shut down the emulator, open the config file at \Users<account>\AppData\Local\AzureStorageEmulator\ and change LoggingEnabled to true. Restart the emulator, and it should start logging to files in the Logs folder there. |
@kfarmer-msft OK, I've got them. What email address should I send them to? |
Hi @isaacabraham, Please email to Thanks! |
Done :-) |
Ping. Any luck with this one? |
@erezvani1529 was my email with logs received? |
cc:/ @kfarmer-msft Hi @isaacabraham , I just checked and yes we have received your email. Apologies for the delay in response. I have followed up internally and we will get back to you with more results soon. Thanks, |
@erezvani1529 ping. it's been nearly two months now - any follow up? |
Four months now. Could you provide an update on this? |
It's been a year now. @erezvani1529 can you provide an update e.g. "won't fix" or something similar? It's hampering our adoption of more Azure services with a customer. |
As you may have heard, we are moving to a completely new emulator. Please try it, and see if it resolves the issue you encountered. |
@kfarmer-msft sorry - are you saying that azurerite is now the replacement for the official storage emulator? |
Related to Azure/azure-webjobs-sdk#53.
Essentially it seems that the later versions of the emulator now do support blob triggers - great news. Unfortunately, if you copy multiple blobs into the local storage emulator at once e.g. 10 or so - you get an HTTP 500 error. This happens deep down so that the the web job does not trigger into application code (although you do see an exception in the webjob application occur).
The text was updated successfully, but these errors were encountered: