-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Durable entities in isolated mode fail on CallEntityAsync #246
Comments
What version of |
|
HI @oleks9o6, are you still experiencing the problem? If so, could you provide a repro? Thanks! |
Hi @lilyjma, Yes, the issue is still reproducible for me. I created a minimal repro example here: https://github.com/oleks9o6/durabletask-dotnet-issues-246. It is durable functions in isolated mode, and runs on .NET 8.0. It also uses MSSQL Server as a storage. The exception from the above occurs when I'm trying to call the durable entity here: https://github.com/oleks9o6/durabletask-dotnet-issues-246/blob/main/src/FunctionApp1/FunctionApp1/Function1.cs#L54. |
If I am not mistaken, mssql does not yet support isolated entities. However, we would expect there to be a better error message than just throwing a null reference exception. |
@sebastianburckhardt is there a recommended fix that should be made in DurableTask.Core to throw a better exception if |
It appears to me that the reason why we get this exception (instead of a normal error message) is that the check that is meant to recognize and report this problem (see |
Closing as this issue is resolved. Check mentioned in above PR is released in DurableTask.Core v2.16.2 |
I'm trying to use durable entities in our project but I'm getting an error when calling an operation on the entity in an orchestrator.
I'm using .NET 8, isolated worker mode, Microsoft.Azure.Functions.Worker.Extensions.DurableTask version is 1.1.0.
That's the call from the orchestrator:
the entity definition is:
but it throws with a null reference
the stack trace is:
The text was updated successfully, but these errors were encountered: