-
Notifications
You must be signed in to change notification settings - Fork 509
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
Add total timeout backend #318
base: main
Are you sure you want to change the base?
Add total timeout backend #318
Conversation
@@ -47,6 +47,8 @@ public enum RetryLogic { | |||
|
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.
@shaileshpadave anything that's under conductor-clients/java/conductor-java-sdk/
is part of the Java Client v4 project.
Let's keep the conductor core changes and client changes in separate PRs
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.
ACK
e922fff
to
e0174b6
Compare
e0174b6
to
7f47427
Compare
@@ -498,6 +498,7 @@ public void testTaskTimeout() { | |||
taskType.setName("test"); | |||
taskType.setTimeoutPolicy(TimeoutPolicy.RETRY); | |||
taskType.setTimeoutSeconds(1); | |||
taskType.setTotalTimeoutSeconds(1_000); |
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.
- Why a
1000
second total timeout for this test? - Is this test covering the changes made to
checkTaskTimeout
?
} | ||
|
||
String reason = | ||
String.format( | ||
"Task timed out after %d seconds. Timeout configured as %d seconds. " | ||
+ "Total Task Timeout configured as %d seconds. " |
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.
This reason
may be confusing.
It's not immediately clear which timeout kicked in since it's mentioning both (timeout and total timeout).
Pull Request type
Changes in this PR
Code changes to check if total task timeout has reached or not, if yes then workflow should be terminated.