-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[Feature-3575][*] Force Task Success #4267
Conversation
更新本地的dev
1. 新添加executeType 2. 新添加对应的commandType 3. 修改controller对应的service部分 4. 补充processService中的verifyIsNeedCreateCommand的判断逻辑
1. 添加两个查询(mapper.java和mapper.xml) 2. 添加ProcessService中constructProcessInstance中对应的部分
update local dev
This reverts commit fa0bb5e.
1. 这样的话可以完整的构建整个dag,恢复之前的上下文;也没有任务可能重复执行的担忧 2. 不需要额外去处理process执行完之后的状态(主要是部分与整体的原因) 3. RecoverNodeIdList也不会重复
1. 失败任务强制成功后会继续submit后续结点 2. 失败重试的节点强制成功后会继续submit后面结点,并且停止retry 3. 对于失败的sub-process如果其中的结点强制成功了,在parent-process中不会有任何影响,只能等到结束后“从强制成功处继续执行”。
1. dataAnalysis 2. alertManager 3. businessTimeUtils的schedule选择
1. taskStateCount中添加了强制成功的状态 2. processStateCount中剔除强制成功的状态
regular update local dev
update local dev
防止logger注入的问题
Codecov Report
@@ Coverage Diff @@
## dev #4267 +/- ##
============================================
+ Coverage 43.23% 43.26% +0.02%
- Complexity 3185 3193 +8
============================================
Files 471 471
Lines 21728 21796 +68
Branches 2626 2639 +13
============================================
+ Hits 9395 9430 +35
- Misses 11438 11469 +31
- Partials 895 897 +2 Continue to review full report at Codecov.
|
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.
front end +1
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.
+1
@@ -414,7 +414,7 @@ private void initTaskQueue() { | |||
if (task.isConditionsTask() || DagHelper.haveConditionsAfterNode(task.getName(), dag)) { | |||
continue; | |||
} | |||
if (task.getState().typeIsFailure() && !task.taskCanRetry()) { | |||
if (task.getState().typeIsFailure() && !task.taskCanRetry() && !task.isConditionsTask()) { |
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.
already judged by the above if.
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.
Ok, I will revise it
I will remove the operation |
any progress? |
Not yet since preparing marriage propose in the past few days. I will finish it today or tomorrow. |
The operation The configuration of force-task-B is as follow: Video Verify: See Video Verify Link |
Kudos, SonarCloud Quality Gate passed! |
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.
+1
great job, and the video gif is very clear
Tips
What is the purpose of the pull request
New Feature: Force Task Success #3726 #3575
FORCED_SUCCESS
resume_from_forced_success
this closes #3726, closes #3575, closes #196
Brief change log
Verify this pull request
(Please pick either of the following options)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Gif Verify:
Video Verify: See Video Verify Link