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

check if workflow is closed when processing sticky timeout timer #458

Merged
merged 1 commit into from
Dec 12, 2017

Conversation

yiminc-zz
Copy link

when processing sticky decision timeout, we need to check if the workflow is already closed.

@@ -783,8 +783,8 @@ Update_History_Loop:
t.metricsClient.IncCounter(metrics.TimerTaskDecisionTimeoutScope, metrics.ScheduleToStartTimeoutCounter)
// decision schedule to start timeout only apply to sticky decision
// check if scheduled decision still pending and not started yet
if isPending && di.Attempt == task.ScheduleAttempt && di.StartedID == emptyEventID &&
msBuilder.isStickyTaskListEnabled() {
if isPending && di.Attempt == task.ScheduleAttempt && && msBuilder.isWorkflowExecutionRunning() &&
Copy link
Contributor

Choose a reason for hiding this comment

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

multiple '&&'. Otherwise looks good.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 66.46% when pulling a0cae6a on yiminc:fix_sticky_timeout into 9314ff5 on uber:master.

@yiminc-zz yiminc-zz merged commit c844eb7 into cadence-workflow:master Dec 12, 2017
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.

3 participants