fix sticky scheduleToStart timeout #408
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Changes Unknown when pulling 4101f73 on yiminc:fix_sticky_timeout into ** on uber:master**. |
yiminc-zz
force-pushed
the
fix_sticky_timeout
branch
from
4101f73
to
b56c9c3
Compare
|
Changes Unknown when pulling b56c9c3 on yiminc:fix_sticky_timeout into ** on uber:master**. |
samarabbas
approved these changes
Nov 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when sticky decision schedule to start timeout fires, we should only re-create decision if the sticky decision was still pending and not started yet.