Repository navigation
fix(actors): Recreate actor object when Dapr reports a new activation - #1876
Conversation
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
…ctivation Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
nelson-parente
left a comment
There was a problem hiding this comment.
#1840 added the gRPC actor event stream after this branched. ActorEventDispatcher on master calls runtime.invoke, invokeReminder and invokeTimer without the activation id, so stream-hosted actors keep the stale object. Can you rebase and pass the id from request.getMetadata() there?
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
Signed-off-by: Cassandra Coyle <cassie@diagrid.io>
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #1876 +/- ##
============================================
+ Coverage 80.69% 80.94% +0.25%
- Complexity 2851 2922 +71
============================================
Files 275 276 +1
Lines 8459 8591 +132
Branches 911 930 +19
============================================
+ Hits 6826 6954 +128
+ Misses 1266 1265 -1
- Partials 367 372 +5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-1.19 release-1.19
# Navigate to the new working tree
cd .worktrees/backport-release-1.19
# Create a new branch
git switch --create backport-1876-to-release-1.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 de80f1f0b0e9d84a0a892f68280af2611eb2f04f
# Push it to GitHub
git push --set-upstream origin backport-1876-to-release-1.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-1.19Then, create a pull request where the |
Pairs with the dapr/dapr change that sends
Dapr-Actor-Activation-Idon actor callbacks.After daprd is killed the app keeps its actor objects, and the new daprd never sends DELETE for them. The SDK reused the stale object, skipped onActivate and kept its in-memory fields.
IllegalStateExceptionActorRuntimeandDaprControllerget overloads with the id, old signatures still workNot covered: a save already in flight can still land late. Etags on actor state are a follow-up.