Open lanfeust69 opened 4 years ago
anthonychu
commented
4 years ago @lanfeust69 Is this a JavaScript app? The issue is tracked here:
https://github.com/Azure/azure-functions-extension-bundles/issues/38
For now, please update your host.json to use an earlier version of the extension bundles. https://github.com/anthonychu/serverless-streamr/commit/4fe4cc78664314af857d2574c2b1d050ebe2ec7d
lanfeust69
commented
4 years ago @anthonychu :
Is this a JavaScript app?
Typescript actually (as the docs say C# is not supported, though I suspect this may no longer be true), but in the end it's of course javascript.
I'm a bit disappointed not to have found the other issue, but clearly it is the same.
For now I worked around the issue by proxying to a standard Function App, which is not 100% straightforward due to CORS issues, but is manageable.
I'll try to take a closer look during the week-end.
Note that I can't access your link any more than @bradygaster can...
anthonychu
commented
4 years ago Whoops had no idea the repo is private. Public now.
anthonychu
commented
4 years ago Also .NET functions are supported now. If you're using .NET, make sure you pull in the latest version of the NuGet. Looks like this was fixed in 1.2.1.
lanfeust69
commented
4 years ago @anthonychu : I checked that rolling ExtensionBundle back to 1.3.2 enabled SignalR binding (and actual operation).
However, I'm a bit skeptical about this line : it seems to me that if actually trying to use a signalRTrigger binding, the resulting exception will be misleading. At least, I tried to add a AzureWebJobsStorage setting (of course pointing to a valide storage account), and that would still crash the function host (when using ExtensionBundle 1.3.3). This strongly suggests that an exception is still raised at that point. There will still be the message from the initial _webHookException, but the part about AzureWebJobsStorage won't be relevant.
anthonychu
commented
4 years ago I think @zackliu has tested for this and can comment on whether this still generates an exception. For what it's worth, I'm using 1.2.2 in a C# function app in static web apps right now and it's working fine.
anthonychu
commented
3 years ago This should be fixed now in the latest Azure Functions extension bundles.
anthonychu
commented
3 years ago Turns out I didn't test this properly. Doesn't look like the updated bundles are fully released yet and problem still exists. The workaround until then is to force the use of bundles version 1.3.2 in host.json:
{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[1.*, 1.3.2]"
}
}
horihiro
commented
3 years ago The same exception message is found when Azure Web PubSub extension is included in the repo as the following link. https://github.com/horihiro/web-pubsub-swa/tree/main/api
Secret initialization from Blob storage failed due to missing both an Azure Storage connection string and a SAS connection uri. For Blob Storage, please provide at least one of these. If you intend to use files for secrets, add an App Setting key 'AzureWebJobsSecretStorageType' with value 'Files'.
And I'm not sure if there is any workaround because the extension is not included in any version of extension bundles yet.
anthonychu
commented
3 years ago This should be fixed for SignalR. Please file an issue with the Web PubSub repo so they can address this.
horihiro
commented
3 years ago FYI. I filed an issue about Web PubSub binding. https://github.com/Azure/azure-sdk-for-net/issues/20854
I'm trying to experiment with Static Web App, I had a small app running fine locally, including using SignalR service for communication.
However, when I actually created the Static Web App, the functions wouldn't work : all I got was "function host is not running". I managed to track this down to the presence of a SignalR binding, for instance :
Having or not the connection string in the settings, or using an
outbinding doesn't change anything.I saw a suggestion to add App Insight, and indeed I got something, namely this exception, much more useful than just "functions host is not running", and seems to correlate :
However, setting the suggested setting
AzureWebJobsSecretStorageTypetoFilesdidn't change anything at all.See also #163, which may or may not be related.