privking opened a new pull request, #15884:
URL: https://github.com/apache/dolphinscheduler/pull/15884

   <!--Thanks very much for contributing to Apache DolphinScheduler, we are 
happy that you want to help us improve DolphinScheduler! -->
   
   ## Purpose of the pull request
   When the task instance is re-executed in the workflow instance, the status 
of the instance (including history status) cannot be seen , and the details 
cannot be seen in the task instance list. But you can see from the log that the 
task has been executed.
   
   I think the cause of this problem is that 
`WorkflowExecuteRunnable.taskCodeInstanceMap` did not remove the corresponding 
instance, and then in the `submitPostNode` method, there was an error in 
determining whether the task instance already existed.
   
   By the way, I modified the `WorkflowExecuteRunnable.completeTaskSet` 
deletion logic in this method
   
   <img width="997" alt="bug" 
src="https://github.com/apache/dolphinscheduler/assets/43061765/5ae089fa-90ea-42f2-82c9-6093537bf949";>
   
   <!--(For example: This pull request adds checkstyle plugin).-->
   
   ## Brief change log
   
   <!--*(for example:)*
   - *Add maven-checkstyle-plugin to root pom.xml*
   -->
   
   ## Verify this pull request
   
   <!--*(Please pick either of the following options)*-->
   
   This pull request is code cleanup without any test coverage.
   
   *(or)*
   
   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:)*
   - *Added dolphinscheduler-dao tests for end-to-end.*
   - *Added CronUtilsTest to verify the change.*
   - *Manually verified the change by testing locally.* -->
   
   (or)
   
   If your pull request contain incompatible change, you should also add it to 
`docs/docs/en/guide/upgrede/incompatible.md`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to