Skip to content
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

Utilize shard clock for child workflow #2746

Merged
merged 1 commit into from
Apr 22, 2022

Conversation

wxing1292
Copy link
Contributor

What changed?

  • Use shard clock for parent / child workflow

Why?
see #2743

How did you test it?
Unit tests

Potential risks
N/A

Is hotfix candidate?
N/A

* Use shard clock for parent / child workflow
@wxing1292 wxing1292 marked this pull request as ready for review April 21, 2022 19:20
@wxing1292 wxing1292 requested a review from a team as a code owner April 21, 2022 19:20
Comment on lines +306 to +309
var parentClock *clockpb.ShardClock
if executionInfo.ParentClock != nil {
parentClock = vclock.NewShardClock(executionInfo.ParentClock.Id, executionInfo.ParentClock.Clock)
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea is to have a deep copy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

@wxing1292 wxing1292 merged commit fa39d14 into temporalio:master Apr 22, 2022
@wxing1292 wxing1292 deleted the citadel-3-child-workflow branch April 22, 2022 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants