You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to what is documented in the source code (Actor.cs), in time of execution of an actor method, if user code throws any exception, all the state changes in the state manager should not be saved.
When an actor call fails, it is imperative that the state is reset.
In the remoting path, we were catching the exception and returning
an error response instead of propagating the exception. Without this,
the error path was never triggered. This allowed for state from
failed requests to persist on subsequent requests.
dapr#762
Signed-off-by: Hal Spang <halspang@microsoft.com>
When an actor call fails, it is imperative that the state is reset.
In the remoting path, we were catching the exception and returning
an error response instead of propagating the exception. Without this,
the error path was never triggered. This allowed for state from
failed requests to persist on subsequent requests.
#762
Signed-off-by: Hal Spang <halspang@microsoft.com>
Expected Behavior
According to what is documented in the source code (Actor.cs), in time of execution of an actor method, if user code throws any exception, all the state changes in the state manager should not be saved.
dotnet-sdk/src/Dapr.Actors/Runtime/Actor.cs
Line 97 in 75bdb8c
Actual Behavior
Actor saves all state changes, regardless of whether there is any exception in the user code or not.
Steps to Reproduce the Problem
After calling the following Actor Method, the state will be saved in the actor state storage.
The text was updated successfully, but these errors were encountered: