From 7bf71e85a1962de45773af499c8b293fc0fa072d Mon Sep 17 00:00:00 2001 From: lile Date: Thu, 23 Jan 2025 15:52:32 +0800 Subject: [PATCH] Fix #16978 AbstractDelayEvent compare method is incorrect-fix CodeQL --- .../master/engine/task/statemachine/TaskFailureStateAction.java | 1 - 1 file changed, 1 deletion(-) diff --git a/dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/engine/task/statemachine/TaskFailureStateAction.java b/dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/engine/task/statemachine/TaskFailureStateAction.java index 63cf2ba9941b..a6af56f2b96e 100644 --- a/dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/engine/task/statemachine/TaskFailureStateAction.java +++ b/dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/engine/task/statemachine/TaskFailureStateAction.java @@ -130,7 +130,6 @@ public void killEventAction(final IWorkflowExecutionRunnable workflowExecutionRu final ITaskExecutionRunnable taskExecutionRunnable, final TaskKillLifecycleEvent taskKillEvent) { throwExceptionIfStateIsNotMatch(taskExecutionRunnable); - final IWorkflowExecutionGraph workflowExecutionGraph = taskExecutionRunnable.getWorkflowExecutionGraph(); // for now, killEventAction can be fired on failure with retry // there is no task executor now, shouldn't call workflowExecutionGraph.isTaskExecutionRunnableActive() // it's better to call super.killedEventAction() direct