Skip to content

[Bug] Improve the scenario of continuing to submit subsequent tasks after failure#12448

Closed
WangJPLeo wants to merge 5 commits intoapache:devfrom
WangJPLeo:failure-continue-fix
Closed

[Bug] Improve the scenario of continuing to submit subsequent tasks after failure#12448
WangJPLeo wants to merge 5 commits intoapache:devfrom
WangJPLeo:failure-continue-fix

Conversation

@WangJPLeo
Copy link
Contributor

@WangJPLeo WangJPLeo commented Oct 19, 2022

Purpose of the pull request

Improve the scenario of continuing to submit subsequent tasks after failure.

Brief change log

  1. Improve the scenario of continuing to submit subsequent tasks after failure, if there are subsequent tasks:
    a. nodes are parallel;
    b. nodes are serial and failed task type is condition;
    c. nodes are serial and next task type is condition;
  2. haveAllNodeAfterNode change to haveAnyNodeAfterNode;
  3. relate [Fix-9717] The failure policy of the task flow takes effect #9718;

Verify this pull request

Manually verified the change by testing locally.

@WangJPLeo WangJPLeo changed the title Improve the scenario of continuing to submit subsequent tasks after failure [Bug] Improve the scenario of continuing to submit subsequent tasks after failure Oct 19, 2022
@WangJPLeo WangJPLeo added this to the 3.1.1 milestone Oct 19, 2022
@WangJPLeo WangJPLeo added the bug Something isn't working label Oct 19, 2022
Comment on lines +428 to +435
if (!DagHelper.haveAnyNodeAfterNode(Long.toString(taskInstance.getTaskCode()), dag)) {
submitPostNode(Long.toString(taskInstance.getTaskCode()));
} else {
if (taskInstance.isConditionsTask()
|| DagHelper.haveConditionsAfterNode(Long.toString(taskInstance.getTaskCode()), dag)) {
submitPostNode(Long.toString(taskInstance.getTaskCode()));
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

could we move these conditions to a private function or workflow util, such as shouldSubmitPostNode? because all these condition should submitPostNode, might be clearer for reading. WDYT.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's excellent, i will improve it.

@zhuangchong zhuangchong modified the milestones: 3.1.1, 3.1.2 Nov 4, 2022
@zhuangchong zhuangchong modified the milestones: 3.1.2, 3.1.3 Dec 7, 2022
@zhuangchong zhuangchong modified the milestones: 3.1.3, 3.1.4 Jan 3, 2023
@zhuangchong zhuangchong modified the milestones: 3.1.4, 3.1.5 Feb 21, 2023
@zhuangchong zhuangchong modified the milestones: 3.1.5, 3.1.6 Apr 6, 2023
@zhuangchong zhuangchong modified the milestones: 3.1.6, 3.2.0 May 10, 2023
@zhongjiajie zhongjiajie modified the milestones: 3.2.0, 3.3.0 Aug 30, 2023
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity for 120 days. It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Jan 26, 2024
@github-actions
Copy link

github-actions bot commented Feb 3, 2024

This pull request has been closed because it has not had recent activity. You could reopen it if you try to continue your work, and anyone who are interested in it are encouraged to continue work on this pull request.

@github-actions github-actions bot closed this Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend bug Something isn't working Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants