System.NotSupportedException: Durable entities are not supported by the current backend configuration #390
Labels
P1
Priority 1
Comments
This was referenced May 2, 2024
|
Just a little update on what I have figured out so far, nothing definitive yet. I am honestly a bit stomped... when debugging your sample app (thank you!) I can see in the debugger that the field and the debugger shows that The problem does not show up in my local build (that is why our tests did not find it), which makes it difficult to debug. |
|
Now I have a debugger attached just after the two lines above... unfortunately the debugger just confirms the weirdness of this. In immediate window: |
|
@sebastianburckhardt thanks for looking into this. On a separate note, is there any documentation that we can follow to debug through (like you are doing?). Yesterday after seeing this issue, I tried debugging through it after downloading the source code for |
No, I am also struggling to figure it out. Somehow it looks in the debugger like an older version of Netherite is being picked up even though your project specifies 1.5.1. But I don't know why that would happen. |
😢
Hmm, interesting. |
|
I am suspecting NuGet package cache issues. This could just be what is happening on my local machine though while I am trying to debug. Not sure if it would actually apply to you. |
|
Noticed there were no integration tests for Durable Entities. Added some: #391 But I am not sure whether these are getting executed, not seeing them running in the PR. |
|
quick theory - I think this is the problem: ^ This file doesn't seem updated, which means the Host process is actually loading an older version of Netherite. That explains what Sebastian was describing here: #390 (comment) |
|
Yep, that was it. That was hard to debug. Having to manually update this file is problematic, leads to release mistakes, so I'll refactor this AssemblyInfo file to be auto-generated. FYI @nytian - we may need to trigger another release here, I'll let you know. |
|
Thanks @davidmrdavid, that makes sense! |
|
Hi @davidmrdavid, do you have an ETA for the release of the new version with the fix you found? This is related to this request done here which is blocking us from testing how Netherite behaves in Isolated mode for a new Durable Function we are developing. Thanks! |
|
@davidmrdavid Has the fix been released? |
|
@bachuv - not yet, we wanted to release the DF extension and .NET isolated packages first, which just came out. It's on my radar. |
|
We're also keen on this release as we're looking at changing our Durable Function isolated worker app storage provider over to use Netherite. 🥳 |
|
I am really interested in this fix being release |
|
Can confirm with, Output of the same example provided above with updated packages:
Thanks @davidmrdavid @sebastianburckhardt! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
durabletask-netherite: 1.5.1 says it added support for
isolated entities, but it still doesn't seem to work.Exception:
Example Project:
AzureFunctionsDemo.Netherite.zip
csproj
host.json
{ "version": "2.0", "extensions": { "durableTask": { "storageProvider": { "type": "Netherite" } } }, "logging": { "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true } } }local.settings.json
{ "IsEncrypted": false, "Values": { "AzureWebJobsStorage": "UseDevelopmentStorage=true", "EventHubsConnection": "SingleHost", "FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated" } }Entity
Function
Verbose Log
The text was updated successfully, but these errors were encountered: