-
Notifications
You must be signed in to change notification settings - Fork 913
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
Refactoring: rename UpdateActivityWithCallback method on mutable state to UpdateActivity #6832
Conversation
18bdf12
to
67c2527
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please also add risk section to PR description saying that some mutable states might start to trigger errors now because their size is computed correctly and will become large than previous incorrect value.
ed6e84a
to
71821cc
Compare
@@ -389,12 +389,13 @@ func (r *TaskRefresherImpl) refreshTasksForActivity( | |||
} | |||
|
|||
if CompareVersionedTransition(minVersionedTransition, EmptyVersionedTransition) == 0 { // Full refresh | |||
// clear activity timer task mask for later activity timer task re-generation | |||
activityInfo.TimerTaskStatus = TimerTaskStatusNone | |||
|
|||
// need to update activity timer task mask for which task is generated | |||
if err := mutableState.UpdateActivity( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What changed?
Why?
Old UpdateActivity was not actually working. ActivityInfo in pending activities is a pointer, so calculating size was wrong. Few other reasons.
How did you test it?
unit tests
Risks
With this change the size of mutable state is calculated properly. This means that in some cases it may change, thus becoming larger then before, and trigger some errors.
Documentation
Is hotfix candidate?
No