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

Fix ExecutionTime backfill by changing init order #1836

Merged
merged 2 commits into from
Aug 18, 2021
Merged

Conversation

dnr
Copy link
Member

@dnr dnr commented Aug 18, 2021

What changed?

Tweak the order of initializing fields so that the backfill ExecutionTime logic works correctly.

Why?

It was calling GetStartEvent before initializing executionState, which contains the run id. Without the run id, the event cache was using a bad key and confusing events from different runs.

How did you test it?

Mostly manual testing and observation.

Potential risks

This only affects the ExecutionTime backfill logic, so shouldn't affect anything that doesn't depend on that.

Is hotfix candidate?

yes

@dnr dnr requested a review from a team August 18, 2021 22:25
@dnr dnr enabled auto-merge (squash) August 18, 2021 22:30
@dnr dnr merged commit 182ae5a into temporalio:master Aug 18, 2021
@dnr dnr mentioned this pull request Aug 18, 2021
@dnr dnr deleted the cron2 branch August 18, 2021 23:16
Ardagan added a commit to Ardagan/temporal that referenced this pull request Sep 21, 2021
Ardagan added a commit to Ardagan/temporal that referenced this pull request Sep 21, 2021
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

3 participants