status
stringclasses 1
value | repo_name
stringclasses 13
values | repo_url
stringclasses 13
values | issue_id
int64 1
104k
| updated_files
stringlengths 11
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 38
55
| pull_url
stringlengths 38
53
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
unknown | language
stringclasses 5
values | commit_datetime
unknown |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,623 | ["dolphinscheduler-ui/src/views/projects/workflow/definition/use-table.ts"] | [Bug] [dolphinscheduler-ui] UI timed scheduler Improvement | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
https://github.com/apache/dolphinscheduler/issues/15449
https://github.com/apache/dolphinscheduler/assets/26395835/6251f961-b426-451f-a6d4-a7207aa771db
### What you expected to happen
在工作流定义中，上线一个已经存在定时配置的任务时，执行update逻辑。
In the workflow definition, the update logic is executed when a task already has a scheduled configuration.
### How to reproduce
在工作流定义中，上线一个已经存在定时配置的任务时，会错误的执行create逻辑。
In the workflow definition, the create logic will be executed incorrectly when a task already has a scheduled configuration.
### Anything else
pass
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15623 | https://github.com/apache/dolphinscheduler/pull/15624 | e3bd26322fcb75f620c5733c6f009823fb74dc3a | e9843002538dec9a21f1ef0383136fc699ff197b | "2024-02-23T11:44:00Z" | java | "2024-03-06T02:02:16Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,616 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/parameters/AbstractParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-shell/src/main/java/org/apache/dolphinscheduler/plugin/task/shell/ShellParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-shell/src/test/java/org/apache/dolphinscheduler/plugin/task/shell/ShellParametersTest.java"] | [Bug] [Worker] Task out param may loss | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Task param may loss due to the task exist out log but not match out param key.
### What you expected to happen
The out param cannot transport successfully.
### How to reproduce
1. Create a Shell echo '${setValue(a=111)}', outparam is b=222
2. Execute the shell find the shell cannot transport out param.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15616 | https://github.com/apache/dolphinscheduler/pull/15617 | 2b4c1e06b67977dfed87fec0a528a1f9b75308d1 | 24ff70dc88dd56112100bb4c8ebad3cfd0da2e18 | "2024-02-22T11:57:35Z" | java | "2024-02-23T03:11:06Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,612 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [Master] Recovery paused workflowInstance may generate failover taskInstance | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When we pause a workflowInstance and recovery it, then will generate failover taskInstance.
This is caused by we try to takeover the paused taskInstance but takeover failed.
<img width="1627" alt="image" src="https://github.com/apache/dolphinscheduler/assets/22415594/3aa4f49e-378f-4fc7-88cb-9b09defc6f8e">
### What you expected to happen
xx
### How to reproduce
1. Run a workflow
2. Pause it
3. Recovery the workflow instance
4. See the task instance status.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15612 | https://github.com/apache/dolphinscheduler/pull/15611 | 5213290262117d78dcd8936dd28eec2002a3e538 | 2b4c1e06b67977dfed87fec0a528a1f9b75308d1 | "2024-02-22T07:04:18Z" | java | "2024-02-22T07:57:08Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,606 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/utils/PageInfo.java"] | [Bug] Version 3.2.1 [Instance list paging is incorrect, the monitored disk capacity is displayed as 0] | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
刚升级到3.2.1，发现实例列表分页失败，还有监控的磁盘容量显示错误 全是0
### What you expected to happen
解决实例列表无法分页问题
### How to reproduce
如上图，3.2.1版本
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15606 | https://github.com/apache/dolphinscheduler/pull/15619 | 24ff70dc88dd56112100bb4c8ebad3cfd0da2e18 | eb2a75b3b798b70e697505b42500e0aacdd45864 | "2024-02-21T05:46:37Z" | java | "2024-02-23T05:57:54Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,575 | ["dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/ProcessInstanceServiceTest.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/mapper/TaskInstanceMapper.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/repository/TaskInstanceDao.java", "dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/TaskInstanceMapper.xml", "dolphinscheduler-dao/src/test/java/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapperTest.java", "dolphinscheduler-dao/src/test/java/org/apache/dolphinscheduler/dao/mapper/TaskInstanceMapperTest.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessService.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessServiceImpl.java"] | [Bug] [Master] Recover then the workflow instance will not restart task instance | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When we kill a workflow instance which contains a failed task instance and recover it.
Then it might go into success, but the workflow instance contains failed task instance.
### What you expected to happen
The workflow instance status is correct with task instance.
### How to reproduce
1. Start a workflow instance which will contains failed task instance and running tasks instance.
2. Kill it and recovery
3. The workflow instance will go into success but it contains failed task instance.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15575 | https://github.com/apache/dolphinscheduler/pull/15574 | 91d56f48601279eeb7de1a057e5c4425f86f2198 | 43a06525a29e01f6769aa0057512884d7441b438 | "2024-02-05T15:14:23Z" | java | "2024-02-06T02:09:30Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,573 | ["dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessServiceImpl.java"] | [Bug] [Master] Master failover will not handle ready_stop and ready_pause workflow instance correctly. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When master failover, if the workflow instance belong to the failover master is ready_stop or ready_pause, then the task instance will not be killed and the workflow instance will go into finished.
This is caused we didn't handle the ready state in failover.
### What you expected to happen
The workflow instance state is correct with task instance state.
### How to reproduce
1. Kill master
2. Stop workflow instance
3. Restart master.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15573 | https://github.com/apache/dolphinscheduler/pull/15572 | 73a5a77db249cbfc69e564557bb067e6febda6d9 | 1b32e28cc821daf940c264fecec23b2225446a67 | "2024-02-05T14:54:14Z" | java | "2024-02-06T07:25:50Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,530 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-http/src/main/java/org/apache/dolphinscheduler/plugin/task/http/HttpParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-http/src/main/java/org/apache/dolphinscheduler/plugin/task/http/HttpTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-http/src/test/java/org/apache/dolphinscheduler/plugin/task/http/HttpTaskTest.java", "dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/locales/zh_CN/project.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-http.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/format-data.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/tasks/use-http.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/types.ts"] | [Improvement][HTTP] support customization of the JSON format in http body | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
The current HTTP task only supports setting the HTTP body through `http_parameters`, and the body only supports JSON format where the value of the JSON is limited to strings. For example:
```json
{
"key1": "value1",
"key2": "value2"
}
```
Allowing customization of the JSON format would further enhance the flexibility of HTTP tasks. For instance, supporting the following format:
```json
{
"key1": "value1",
"key2": {
"int": 123,
"boolean": true,
"array": [1, 2, 3]
}
}
```
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15530 | https://github.com/apache/dolphinscheduler/pull/15531 | 86ef9666c4caca83b703b742e07e5d371f3f4835 | 3640a2834848765f796ed1b6ba5e832657069332 | "2024-01-29T12:04:41Z" | java | "2024-01-31T03:02:48Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,524 | [".github/workflows/backend.yml", "dolphinscheduler-dao/src/test/java/org/apache/dolphinscheduler/dao/mapper/AuditLogMapperTest.java"] | [Bug] [CI] 3.1.8 download failed | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The link of https://dlcdn.apache.org/dolphinscheduler/3.1.8/apache-dolphinscheduler-3.1.8-bin.tar.gz is 404.
<img width="1110" alt="image" src="https://github.com/apache/dolphinscheduler/assets/22415594/abf6b557-e957-4f12-8cfa-f5dc1808844e">
<img width="1088" alt="image" src="https://github.com/apache/dolphinscheduler/assets/22415594/da219928-55ab-462b-839a-b6ee72e2b3db">
### What you expected to happen
xx
### How to reproduce
xx
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15524 | https://github.com/apache/dolphinscheduler/pull/15526 | 431414729fc9a75ba04a6dc01a196f4dd3660557 | 419cb49311d3e5aa7a04544efe46359f3802afba | "2024-01-25T16:10:36Z" | java | "2024-01-26T07:07:05Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,500 | ["docs/docs/en/guide/task/flink.md", "docs/docs/en/guide/task/spark.md", "docs/docs/zh/guide/task/flink.md", "docs/docs/zh/guide/task/spark.md"] | [Doc][Task] Update cli opts of spark and flink | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Update cli opts of spark and flink
### Documentation Links
_No response_
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15500 | https://github.com/apache/dolphinscheduler/pull/15501 | 603dfa2e4b38215afec05444789f09328507d48d | e4de06b5af1c42299a72988f356b8f611e8cf431 | "2024-01-17T05:40:53Z" | java | "2024-01-17T06:22:27Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,491 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/K8sNamespaceController.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/K8sNamespaceService.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/K8SNamespaceServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/K8SNamespaceServiceTest.java"] | [Bug] [dolphinscheduler-api-->K8sNamespaceController-->createK8sNamespace] create namespace, if not exist on k8s,will don't create | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
k8s操作报错[namespace dev_now does not exist in k8s cluster, please create namespace in k8s cluster first].
method createK8sNamespace notes： create namespace,if not exist on k8s,will create,if exist only register in db，but this method **don't** create on k8s when not exist on k8s.
### What you expected to happen
create namespace,if not exist on k8s,**will create on k8s**,if exist only register in db
### How to reproduce
ui create namespace dev-xx when not exist on k8s
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15491 | https://github.com/apache/dolphinscheduler/pull/15546 | 25810a81dc528feedd81e44f8f57469286c0e8c7 | 2f66a667ba6bed20003cfb17af3f347166e678c1 | "2024-01-16T06:49:14Z" | java | "2024-02-01T02:39:54Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,483 | ["docs/docs/en/guide/installation/kubernetes.md", "docs/docs/zh/guide/installation/kubernetes.md"] | [Doc][K8S] Add DS K8S Operator into `k8s deployment character` | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
maybe we can add k8s operator into character 'k8s deployment'.
I thought helm is the only way to deploy ds before I knew https://github.com/apache/dolphinscheduler-operator
### Documentation Links
https://dolphinscheduler.apache.org/zh-cn/docs/3.2.0/guide/installation/kubernetes
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15483 | https://github.com/apache/dolphinscheduler/pull/15516 | 95ae0036f6c0f129af20e8a0423e7085fc8993f2 | 8abb5e55b7f3ad12d4c33163927471bcbeab6c5d | "2024-01-14T08:52:21Z" | java | "2024-01-24T03:10:58Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,480 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/ProcessUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/test/java/org/apache/dolphinscheduler/plugin/task/api/utils/ProcessUtilsTest.java"] | [Bug] [Task Api] The MACPATTERN in ProcessUtils does not cover all cases on MacOS and ProcessUtilsTest failed on MacOS | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
**org.apache.dolphinscheduler.plugin.task.api.utils.ProcessUtils**
------
The is the `MACPATTERN` in `ProcessUtils`:
```
private static final Pattern MACPATTERN = Pattern.compile("-[+|-]-\\s(\\d+)");
```
and the `getPidsStr` method is:
```
public static String getPidsStr(int processId) throws Exception {
StringBuilder sb = new StringBuilder();
Matcher mat = null;
// pstree pid get sub pids
if (SystemUtils.IS_OS_MAC) {
String pids = OSUtils.exeCmd(String.format("%s -sp %d", TaskConstants.PSTREE, processId));
if (StringUtils.isNotEmpty(pids)) {
mat = MACPATTERN.matcher(pids);
}
} else if (SystemUtils.IS_OS_LINUX) {
String pids = OSUtils.exeCmd(String.format("%s -p %d", TaskConstants.PSTREE, processId));
if (StringUtils.isNotEmpty(pids)) {
mat = LINUXPATTERN.matcher(pids);
}
} else {
String pids = OSUtils.exeCmd(String.format("%s -p %d", TaskConstants.PSTREE, processId));
if (StringUtils.isNotEmpty(pids)) {
mat = WINDOWSPATTERN.matcher(pids);
}
}
if (null != mat) {
while (mat.find()) {
sb.append(mat.group(1)).append(" ");
}
}
return sb.toString().trim();
}
```
when I executed `pstree -sp` in MacOS, this was all the case:
`pstree -sp 04619`
```
-+= 04619 xxxxxx /Applications/IntelliJ IDEA.app/Contents/MacOS/idea
|--- 04626 xxxxxx /Applications/IntelliJ IDEA.app/Contents/bin/fsnotifier
|--- 04730 xxxxxx /Users/xxxxxx/Library/Java/JavaVirtualMachines/corretto-17.0.8.1/Contents/Home/bin/java -Djava.awt.headless=true -Dmaven.defaultProjectBuilder.disableGlobalModelCache=true -D
|--- 04997 xxxxxx /Applications/IntelliJ IDEA.app/Contents/jbr/Contents/Home/bin/java -Xmx1024m -Didea.version=2023.2.5 -Dfile.encoding=UTF-8 -classpath /Applications/IntelliJ IDEA.app/Contents/lib
\--= 04769 xxxxxx /bin/zsh --login -i
```
`pstree -sp 04642`
```
-+= 04642 xxxxxx /Applications/Docker.app/Contents/MacOS/com.docker.backend
|--- 04656 xxxxxx docker serve --address unix:///Users/xxxxxx/.docker/run/docker-cli-api.sock
|--- 04658 xxxxxx com.docker.extensions -address /Users/xxxxxx/Library/Containers/com.docker.docker/Data/extension-manager.sock -watchdog
|--- 04659 xxxxxx com.docker.dev-envs -watchdog
|--- 04660 xxxxxx com.docker.build
|--- 04661 xxxxxx /Applications/Docker.app/Contents/MacOS/com.docker.virtualization --kernel /Applications/Docker.app/Contents/Resources/linuxkit/kernel --cmdline init=/init loglevel=1 root=/dev/vd
\-+- 04685 xxxxxx /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/MacOS/Docker Desktop --name=dashboard
|--- 04692 xxxxxx /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (GPU).app/Contents/MacOS/Docker Desktop Helper (GPU) --type=gpu-process --us
|--- 04693 xxxxxx /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper.app/Contents/MacOS/Docker Desktop Helper --type=utility --utility-sub-type=n
|--- 04696 xxxxxx /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (Renderer).app/Contents/MacOS/Docker Desktop Helper (Renderer) --type=render
|--- 04700 xxxxxx /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (Renderer).app/Contents/MacOS/Docker Desktop Helper (Renderer) --type=render
|-+- 06650 xxxxxx /Applications/Docker.app/Contents/Resources/bin/docker stats --all --no-trunc --no-stream --format {{ json .}}
| \--- 06651 xxxxxx /Applications/Docker.app/Contents/Resources/bin/com.docker.cli stats --all --no-trunc --no-stream --format {{ json .}}
\-+- 06652 xxxxxx /Applications/Docker.app/Contents/Resources/bin/docker stats --all --no-trunc --no-stream --format {{ json .}}
\--- 06653 xxxxxx /Applications/Docker.app/Contents/Resources/bin/com.docker.cli stats --all --no-trunc --no-stream --format {{ json .}}
```
The conclusion drawn from the above results is: there are a total of 4 types of output: '-+=', '--=', '-+-', and '---', but the pattern: `-[+|-]-\\s(\\d+)` only covers 2 types: '-+-' and '---'.
**org.apache.dolphinscheduler.plugin.task.api.utils.ProcessUtilsTest**
------
In `ProcessUtilsTest`, the `testGetPidsStr` only considers linux scenario:
```
String pids = "sudo(6279)---558_1497.sh(6282)---sleep(6354)";
int processId = 6279;
String exceptPidsStr = "6279 6282 6354";
String command;
MockedStatic<OSUtils> osUtilsMockedStatic = Mockito.mockStatic(OSUtils.class);
if (SystemUtils.IS_OS_MAC) {
command = String.format("%s -sp %d", TaskConstants.PSTREE, processId);
} else if (SystemUtils.IS_OS_LINUX) {
command = String.format("%s -p %d", TaskConstants.PSTREE, processId);
} else {
command = String.format("%s -p %d", TaskConstants.PSTREE, processId);
}
osUtilsMockedStatic.when(() -> OSUtils.exeCmd(command)).thenReturn(pids);
String actualPidsStr = ProcessUtils.getPidsStr(processId);
Assertions.assertEquals(exceptPidsStr, actualPidsStr);
```
If you run this test on MacOS, you get this error:
```
org.opentest4j.AssertionFailedError:
Expected :6279 6282 6354
Actual :
```
### What you expected to happen
The `MACPATTERN` in `ProcessUtils` should cover all MacOS cases and run unit tests successfully on MacOS.
### How to reproduce
Run the`getPidsStr` method in `ProcessUtils` on MacOS.
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15480 | https://github.com/apache/dolphinscheduler/pull/15529 | ef9ed3db55cb1647886b06c2b2c6a5cfcdccfb5c | 4d6af516b9bbc1587318f9a305d82b461c124a30 | "2024-01-13T04:47:20Z" | java | "2024-02-05T03:41:21Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,476 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-java/src/main/java/org/apache/dolphinscheduler/plugin/task/java/JavaTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-java/src/test/java/org/apache/dolphinscheduler/plugin/task/java/JavaTaskTest.java"] | [Bug] [Task] java task args erro | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
java -help It's a classpath, not a class-path
### What you expected to happen
java -help It's a classpath, not a class-path
### How to reproduce
modify task args
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15476 | https://github.com/apache/dolphinscheduler/pull/15470 | 0f7081be10b657184d2eef316c8a2cafcf2ce343 | bd48c991783b2e0ea0c602f6ef6c9a09c92e7b42 | "2024-01-12T06:38:33Z" | java | "2024-01-12T06:39:59Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,446 | ["README.md", "README_zh_CN.md"] | [Doc][ReadMe] Add link in dophinscheduler mail list | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
like button 'subscribe to list' https://lists.apache.org/[email protected] and other doc website
### Documentation Links
https://lists.apache.org/[email protected]
https://flink.apache.org/what-is-flink/community/
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15446 | https://github.com/apache/dolphinscheduler/pull/15447 | dcf69cad20642ffac3418b90ce9b7ea8c8ab29f1 | e00121b44bff273a23dd7447d6027698edf73458 | "2024-01-09T10:46:08Z" | java | "2024-01-19T07:33:53Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,426 | ["dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/AuditLogMapper.xml", "dolphinscheduler-dao/src/test/java/org/apache/dolphinscheduler/dao/mapper/AuditLogMapperTest.java"] | [Bug] [Audit log] UI query error | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When db has `PROJECT` type data, ui will throw exception
<img width="1138" alt="image" src="https://github.com/apache/dolphinscheduler/assets/20885366/b09615d2-eeae-4922-8dc4-bb398c5e4b0a">
### What you expected to happen
Shows normally
### How to reproduce
Change the code
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15426 | https://github.com/apache/dolphinscheduler/pull/15427 | 4c31e19e110ab198dbe666718c6db151a43a0852 | e5a512803ec6f8728fe05f4a5433231ab1d13c7e | "2024-01-04T09:02:26Z" | java | "2024-01-05T05:25:54Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,396 | ["dolphinscheduler-worker/src/main/java/org/apache/dolphinscheduler/server/worker/registry/WorkerStopStrategy.java", "dolphinscheduler-worker/src/main/java/org/apache/dolphinscheduler/server/worker/registry/WorkerWaitingStrategy.java", "dolphinscheduler-worker/src/test/java/org/apache/dolphinscheduler/server/worker/registry/WorkerConnectionStateListenerTest.java", "dolphinscheduler-worker/src/test/java/org/apache/dolphinscheduler/server/worker/registry/WorkerRegistryClientTest.java", "dolphinscheduler-worker/src/test/java/org/apache/dolphinscheduler/server/worker/registry/WorkerStrategyTest.java"] | [Improvement][Unit Tests] Improve DolphinScheduler Worker unit tests | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
part of https://github.com/apache/dolphinscheduler/issues/10573
improve dophinscheduler-worker UT
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15396 | https://github.com/apache/dolphinscheduler/pull/15380 | 43a06525a29e01f6769aa0057512884d7441b438 | 69676b445c6a87dbd97c8bfd5797a26600e1bef6 | "2024-01-03T07:41:23Z" | java | "2024-02-06T02:45:53Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,389 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/k8s/impl/K8sTaskExecutor.java"] | [Improvement][K8S]Optimize MDC for K8S tasks | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
```
[INFO] 2024-01-02 19:50:01.365 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[335] - [WorkflowInstance-96941][TaskInstance-102599] - [K8sJobExecutor-mem-monitor-102599] start to submit job
[INFO] 2024-01-02 19:50:01.497 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[340] - [WorkflowInstance-96941][TaskInstance-102599] - [K8sJobExecutor-mem-monitor-102599] submitted job successfully
[INFO] 2024-01-02 19:50:01.503 +0800 o.a.d.server.worker.runner.listener.TaskInstanceExecutionRunningEventAckListenFunction:[44] - [WorkflowInstance-0][TaskInstance-102599] - Receive TaskInstanceExecutionRunningEventAck: TaskInstanceExecutionRunningEventAck(taskInstanceId=102599, success=true)
[INFO] 2024-01-02 19:50:01.506 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[205] - [WorkflowInstance-0][TaskInstance-0] - event received : job:mem-monitor-102599 action:ADDED
[INFO] 2024-01-02 19:50:01.560 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[205] - [WorkflowInstance-0][TaskInstance-0] - event received : job:mem-monitor-102599 action:MODIFIED
[INFO] 2024-01-02 19:50:01.560 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[212] - [WorkflowInstance-0][TaskInstance-0] - job mem-monitor-102599 status 1
[INFO] 2024-01-02 19:50:03.864 +0800 org.apache.dolphinscheduler.plugin.task.api.AbstractTask:[265] - [WorkflowInstance-0][TaskInstance-0] - [K8S-pod-log] error: node
```
The above log, in the k8s task log, both the WorkflowInstanceID and TaskInstanceID are missing.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15389 | https://github.com/apache/dolphinscheduler/pull/15390 | e4de06b5af1c42299a72988f356b8f611e8cf431 | c7a11ce6ed8b606671b4f1fa06b522a72aed50d4 | "2024-01-02T12:00:40Z" | java | "2024-01-17T09:56:11Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,382 | ["dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/locales/zh_CN/project.ts", "dolphinscheduler-ui/src/views/projects/workflow/definition/components/start-modal.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/components/timing-modal.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/components/use-form.ts"] | [Improvement][workFlow] adjust the sequence of alarm group and add validate | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15382 | https://github.com/apache/dolphinscheduler/pull/15384 | bf2cdc530065b5ef121752a12b7c57de92281711 | fd74cf16cbc7be39b02a6bd688ea5633f9757a83 | "2023-12-29T07:16:41Z" | java | "2024-01-02T09:36:30Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,378 | ["dolphinscheduler-ui/src/views/projects/workflow/definition/components/start-modal.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/components/timing-modal.tsx", "dolphinscheduler-ui/src/views/security/worker-group-manage/components/worker-group-modal.tsx"] | [Improvement][workGroup & workFlow] Add workerGroup, workflow ; dropdowns filter | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15378 | https://github.com/apache/dolphinscheduler/pull/15379 | 1c1d4bd59297942499a8242066de1c8ae0143a58 | c3ffb1330de88e9fa8cd0368a0d0991d076ae53c | "2023-12-28T11:47:26Z" | java | "2023-12-29T05:29:09Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,370 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/registry/ServerNodeManager.java", "dolphinscheduler-master/src/test/java/org/apache/dolphinscheduler/server/master/registry/ServerNodeManagerTest.java"] | [Bug] [Master] When a worker offline, the master still tries to dispatch tasks to the worker and throws an exception | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When a worker offline, there is a chance that the master will continue to send tasks to this worker and throw an exception:
[ERROR] 2023-12-20 22:58:25.317 +0800 org.apache.dolphinscheduler.server.master.runner.GlobalTaskDispatchWaitingQueueLooper:[87] - [WorkflowInstance-0][TaskInstance-0] - Dispatch task failed
org.apache.dolphinscheduler.server.master.exception.TaskDispatchException: Dispatch task to 192.168.1.128:1234 failed
at org.apache.dolphinscheduler.server.master.runner.BaseTaskDispatcher.doDispatch(BaseTaskDispatcher.java:101)
at org.apache.dolphinscheduler.server.master.runner.BaseTaskDispatcher.dispatchTask(BaseTaskDispatcher.java:74)
at org.apache.dolphinscheduler.server.master.runner.GlobalTaskDispatchWaitingQueueLooper.run(GlobalTaskDispatchWaitingQueueLooper.java:79)
Caused by: org.apache.dolphinscheduler.remote.exceptions.RemotingException: connect to : Host(ip=192.168.1.128, port=1234) fail
at org.apache.dolphinscheduler.remote.NettyRemotingClient.sendSync(NettyRemotingClient.java:210)
at org.apache.dolphinscheduler.server.master.rpc.MasterRpcClient.sendSyncCommand(MasterRpcClient.java:49)
at org.apache.dolphinscheduler.server.master.runner.BaseTaskDispatcher.doDispatch(BaseTaskDispatcher.java:87)
### What you expected to happen
When the worker is offline, clear the worker node information in the master and do not attempt to send tasks to it
### How to reproduce
1. Run master-1 and worker-1 server
2. Run worker-2 server. All worker services are in the default worker group
3. kill worker-1 server
4. Running a workflow consists of a number of tasks
5. Some exceptions will be printed to the master log
in addition,
we can debug master server at `org.apache.dolphinscheduler.server.master.registry.ServerNodeManager#updateWorkerNodes()`, We can find that when a worker is offline, the master does not clear the offline worker information in `workerNodeInfo`
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15370 | https://github.com/apache/dolphinscheduler/pull/15459 | feb302335bc0c0519f19cf6dc730c965a1f06d35 | 431414729fc9a75ba04a6dc01a196f4dd3660557 | "2023-12-27T11:37:11Z" | java | "2024-01-25T10:10:36Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,368 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/k8s/impl/K8sTaskExecutor.java"] | [Improvement][K8S] Custom label of a K8S task can be passed to the pod | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
For [apply policies using dynamic admission control](https://kubernetes.io/docs/concepts/policy/#apply-policies-using-dynamic-admission-control), the support for passing the custom label of a K8s task to the pod will bring more convenience.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15368 | https://github.com/apache/dolphinscheduler/pull/15369 | d6dea4633c3f0e89f245b4ebae4c607b8cbde733 | 93ea5f64c31311ab066d2093dbecd6e2f4215c68 | "2023-12-27T01:54:38Z" | java | "2023-12-28T05:49:29Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,349 | ["dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-resources.ts"] | [Bug] [Workflow Definition] [UI] Non-existent resource front ends cannot be culled | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
After a resource is deleted or its name is changed, the resource referenced by the current task node cannot be displayed or deleted. As a result, a message indicating that the resource does not exist is displayed during task running
### What you expected to happen
It should be possible to remove non-existent resource options
### How to reproduce
Select the resource, save the workflow, and go to the resource center to change the reference resource name
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15349 | https://github.com/apache/dolphinscheduler/pull/15350 | 4e069991c738fba17860e129a7d7a10fac76eae3 | c849501f3bed35024bca008477b31e1ad76ce8ff | "2023-12-21T10:21:05Z" | java | "2023-12-26T03:07:43Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,315 | ["dolphinscheduler-ui/src/views/projects/task/components/node/use-task.ts"] | [Bug] [UI] Paused in debugger when create task | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
- Paused in debugger when create task of console
<img width="811" alt="image" src="https://github.com/apache/dolphinscheduler/assets/8847400/57450833-36f2-4056-be6b-8efac43f8f83">
### What you expected to happen
open task modal
### How to reproduce
- Open the browser console
- Drag the task to the dag canvas
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15315 | https://github.com/apache/dolphinscheduler/pull/15316 | f921457a55fe09629d2ce23b1e0272c3ed8c9824 | b7ffa7453768f0730ecca25fbd04478e0cc509ed | "2023-12-14T02:25:15Z" | java | "2023-12-21T14:32:09Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,280 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/expand/CuringParamsService.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/expand/CuringParamsServiceImpl.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessService.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessServiceImpl.java", "dolphinscheduler-service/src/test/java/org/apache/dolphinscheduler/service/expand/CuringParamsServiceTest.java"] | [Bug] [parameter] StartParams can't update local params | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When create a workflow, user can set local params in node definition, like the picture below
When start a new instanse by webUI, user can set the param value,
But according to the document, the priority of params,
> The priority of DolphinScheduler parameters from high to low is: Startup Parameter > Local Parameter > Parameter Context > Global Parameter > Project-level Parameter.
In this case, the value of *datat* should be "bbbb", but actually, the value of datat is "aaa" which seted in local param.
### What you expected to happen
according to the document, the priority of params,
> The priority of DolphinScheduler parameters from high to low is: Startup Parameter > Local Parameter > Parameter Context > Global Parameter > Project-level Parameter.
I think Startup Parameter will update local Parameter
### How to reproduce
Step1:
Create a workflow, add a shell task.
Step2:
Edit shell task, add stript:
```shell
echo ${datat}
```
and add a param "datat", default value is "aaa" and then save this workflow.
Step3:
Start this workflow, and add a startup params, **datat**, set the value to "bbb"
Step4:
Check the task log, the value of param *datat* is still 'aaa'
```
[INFO] 2023-12-05 14:20:24.185 +0800 - process start, process id is: 11226
[INFO] 2023-12-05 14:20:25.185 +0800 - ->
aaa
[INFO] 2023-12-05 14:20:25.186 +0800 - process has exited. execute
```
I check the log,
```json
"prepareParamsMap" : {
...
"datat" : {
"prop" : "datat",
"direct" : "IN",
"type" : "VARCHAR",
"value" : "aaa"
},
...
"StartParams" : {
"prop" : "StartParams",
"direct" : "IN",
"type" : "VARCHAR",
"value" : "{\"datat\":\"bbbb\"}"
}
...
}
```
### Anything else
Did I misunderstand the document and the type of Parameter ?
### Version
3.2.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15280 | https://github.com/apache/dolphinscheduler/pull/15544 | e5a208f363abcb31bb7e8ffee16c7a142671c667 | 01eb8f834ff4abf662b704379f1bcd019f4d2d74 | "2023-12-05T07:00:30Z" | java | "2024-02-05T08:17:30Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,215 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/UsersServiceTest.java"] | [Bug] [API] Users are not allowed to modify the default tenant and queue through the update API | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Users can modify the default tenant and queue through the update api. I think this should not be allowed because it cannot be modified through the UI. This should be consistent.
### What you expected to happen
Users are not allowed to modify the default tenant and queue through the update API
### How to reproduce
https://lists.apache.org/thread/89tkm3lmqlzbtm86kx3xnk8cc1smfm83
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15215 | https://github.com/apache/dolphinscheduler/pull/15254 | ef2e9c9b67e03b941ac3e8b6c2a77d4b1d564351 | 7bfc6dc3cfde4acc2f2bc232b8403fd776ed52f2 | "2023-11-24T02:20:58Z" | java | "2023-12-04T02:20:34Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,172 | ["dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpAlertChannelFactory.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpAlertConstants.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/test/java/org/apache/dolphinscheduler/plugin/alert/http/HttpAlertChannelFactoryTest.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/test/java/org/apache/dolphinscheduler/plugin/alert/http/HttpAlertChannelTest.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/test/java/org/apache/dolphinscheduler/plugin/alert/http/HttpSenderTest.java", "dolphinscheduler-ui/src/locales/en_US/security.ts", "dolphinscheduler-ui/src/locales/zh_CN/security.ts"] | [Improvement][Alert] Add timeout params for HTTP plugin | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Add timeout params for HTTP plugin
### Are you willing to submit a PR?
- [X] #15173
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15172 | https://github.com/apache/dolphinscheduler/pull/15174 | 36f72056a9b692ffdc0a57acc0a20690a8b02de9 | a158f1403f82ee0e5443cc6975287634177392cb | "2023-11-16T09:51:41Z" | java | "2023-11-18T14:28:29Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,159 | ["dolphinscheduler-ui/src/views/projects/workflow/instance/index.tsx"] | [Bug] [UI] Workflow instance delete button display error | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
* Workflow instance delete button display error
### What you expected to happen
* see above
### How to reproduce
* see above
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15159 | https://github.com/apache/dolphinscheduler/pull/15160 | 6096c58cb7049783b8f67e790e6a5d62969a4bdf | b8e942208e7dedb06e5bdc6049700fc46df24097 | "2023-11-14T09:20:01Z" | java | "2023-11-14T10:05:06Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,142 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/TaskInstanceServiceImpl.java"] | [Bug] [Task instance] Forced success, running time does not stop | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The task instance is forced successfully and the running time does not stop
### What you expected to happen
The task has ended and the running time has stopped
### How to reproduce
The task is scheduled to machine A, and then KILLs the worker directly, and another machine will be retried. At this time, the task is successfully executed, and then the previous task performs a forced success operation, but the running time does not stop.
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15142 | https://github.com/apache/dolphinscheduler/pull/15144 | d8e820c4b9fa70e6d7c8368a8dc17082f8b15db0 | e5a208f363abcb31bb7e8ffee16c7a142671c667 | "2023-11-08T09:02:36Z" | java | "2024-02-05T06:23:16Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,137 | ["dolphinscheduler-ui/src/views/resource/components/resource/edit/index.tsx", "dolphinscheduler-ui/src/views/resource/components/resource/table/table-action.tsx", "dolphinscheduler-ui/src/views/resource/components/resource/types.ts"] | [Improvement][Resource Center] Display brief file name in file-details page | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
hadoop集群与dolphin是分开部署的，不知道这个需要怎么配置，才能显示不是全路径的，只显示文件名称
### What you expected to happen
hadoop集群与dolphin是分开部署的，不知道这个需要怎么配置，才能显示不是全路径的，只显示文件名称
### How to reproduce
hadoop集群与dolphin是分开部署的，不知道这个需要怎么配置，才能显示不是全路径的，只显示文件名称
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15137 | https://github.com/apache/dolphinscheduler/pull/15175 | a158f1403f82ee0e5443cc6975287634177392cb | 2b4edb3815035e75cd4189ebb9e81be6eee7085b | "2023-11-08T03:28:49Z" | java | "2023-11-19T03:50:53Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,136 | ["docs/docs/en/guide/parameter/context.md", "docs/docs/zh/guide/parameter/context.md"] | [Bug] [setValue] if "\n" in variable, then setValue function will work bad | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
In python task , if a variable has "\n"， then use setValue to make a Parameter for next node, the variable will not work well
node_one
```python
s = "hello \n world"
print("${setValue(message=%s)}"%s)
```
node_two
```shell
echo "${message}"
echo "hi"
```
check runtime log
node_one
```
[INFO] 2023-11-08 10:51:02.588 +0800 - process start, process id is: 10376
[INFO] 2023-11-08 10:51:03.588 +0800 - ->
world)}
[INFO] 2023-11-08 10:51:03.590 +0800 - process has exited. execute
```
node_two
```
[INFO] 2023-11-08 10:51:04.374 +0800 - process start, process id is: 30190
[INFO] 2023-11-08 10:51:05.374 +0800 - ->
hi
[INFO] 2023-11-08 10:51:05.375 +0800 - process has exited. execute
```
### What you expected to happen
In node_two, when `echo "${message}"` will show the Parameter set in pre task, in this case, want show “hello \n world"
### How to reproduce
create a workflow, the first task use python task, make a variable include "\n", then use setValue to make a Parameter
### Anything else
_No response_
### Version
3.2.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15136 | https://github.com/apache/dolphinscheduler/pull/15145 | b8e942208e7dedb06e5bdc6049700fc46df24097 | 3149928cdcde0007b03ab98bc42063d631e52988 | "2023-11-08T03:09:57Z" | java | "2023-11-15T01:30:37Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,114 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/am/KubernetesApplicationManager.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/k8s/impl/K8sTaskExecutor.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/parameters/AbstractParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/parameters/K8sTaskParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-k8s/src/main/java/org/apache/dolphinscheduler/plugin/task/k8s/K8sTask.java"] | [Bug] K8sTaskExecutionContext incorrectly set configYaml | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
```java
private KubernetesClient getClient(KubernetesApplicationManagerContext kubernetesApplicationManagerContext) {
K8sTaskExecutionContext k8sTaskExecutionContext =
kubernetesApplicationManagerContext.getK8sTaskExecutionContext();
k8sTaskExecutionContext
.setConfigYaml(JSONUtils.getNodeString(k8sTaskExecutionContext.getConnectionParams(), "kubeConfig"));
return cacheClientMap.computeIfAbsent(kubernetesApplicationManagerContext.getLabelValue(),
key -> new KubernetesClientBuilder()
.withConfig(Config.fromKubeconfig(k8sTaskExecutionContext.getConfigYaml())).build());
}
```
```java
k8sTaskExecutionContext
.setConfigYaml(JSONUtils.getNodeString(k8sTaskExecutionContext.getConnectionParams(), "kubeConfig"));
```
We can not directly change this. For normal task, like `spark` on k8s, `k8sTaskExecutionContext` is constructed by `TaskExecutionContextFactory`, when they call `getClient`, `connectionParams` is `null`.
### What you expected to happen
set configYaml during K8S task initialization
### How to reproduce
run `spark` task
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15114 | https://github.com/apache/dolphinscheduler/pull/15116 | 159179ac95dd5dfc960ee0a6c341c7b67ec97941 | ce11674668cf26747f34c3474763c32e1ba5b6d1 | "2023-11-03T07:01:36Z" | java | "2023-12-14T13:34:42Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,072 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/ResourcesServiceImpl.java"] | When a non-admin account uploads files in the resource center, the workflow definition Spark type task main package cannot be referenced. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When a non-admin account uploads files in the resource center, the workflow definition Spark type task main package cannot be referenced.
And no records are inserted into the metadata table, and the api-server does not report an error.
### What you expected to happen
The upload resource interface is abnormal, resulting in no records being inserted into the metadata.
### How to reproduce
Upload files and create spark type tasks
### Anything else
1
### Version
3.2.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
-------------
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
非admin账号在资源中心上传文件，工作流定义Spark类型任务主程序包无法引用
且元数据表中没有插入记录，api-server也没有报错
### What you expected to happen
上传资源接口异常，导致没有在元数据中插入记录
### How to reproduce
上传文件，并创建spark类型任务
### Anything else
1
### Version
3.2.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [ ] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15072 | https://github.com/apache/dolphinscheduler/pull/15097 | d5f99cc582a2ad518715c5c02d08dd5f315dd33b | dc503b0e00dd0b25f810e5b8dd3496a1efa1fede | "2023-10-24T07:04:37Z" | java | "2023-11-02T05:34:30Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,048 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-sql/src/main/java/org/apache/dolphinscheduler/plugin/task/sql/SqlTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-sql/src/main/java/org/apache/dolphinscheduler/plugin/task/sql/utils/SqlSplitUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-sql/src/test/java/org/apache/dolphinscheduler/plugin/task/sql/SqlTaskTest.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-sql/src/test/java/org/apache/dolphinscheduler/plugin/task/sql/utils/SqlSplitUtilsTest.java"] | [Bug] [API] sql default separator is ;\n , but save sql content to ds database, it display ;\r\n | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
I create sql task in 3.2.0 version. write two sql command in one sql task. use ;\n to separate it. but it execute fail.
i view database in ds. it save ;\r\n, not ;\n. cause not correctly separate it.
我安装了一个3.2.0版本的dolphinscheduler，创建了一个Sql任务，任务里面编写了两个SQL，然后执行执行失败。
### What you expected to happen
because ;\n is default sql separator, write more sql command in one sql task, it should separate it correctly.
因为3.2.0版本的dophinscheduler中sql任务的默认分隔符是;\n，正常来说应该能够正常执行。
### How to reproduce
1. create a sql task.
2. write two sql command in created sql task. for example
```
select current_date();
select current_date()
```
3. execute online
4. start execute
1. 创建一个Sql任务
2. 在创建的Sql任务里面添加两个sql命令，例如
```
select current_date();
select current_date();
```
3. 上线工作流
4. 执行工作流
### Anything else
跟踪代码发现，存储到数据库中的sql分隔符是;\r\n,导致代码无法正常分割多个SQL，最终sql任务执行失败。
### Version
3.2.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15048 | https://github.com/apache/dolphinscheduler/pull/15062 | a5284e40242eea7597e7be27d62e3133546e7073 | 99214d0fc387d5d26adde13707405d0d9104e001 | "2023-10-19T06:34:44Z" | java | "2023-10-26T11:50:32Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,036 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/TaskDefinitionServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/TaskDefinitionServiceImplTest.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/mapper/ProcessTaskRelationMapper.java", "dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessTaskRelationMapper.xml"] | [Bug] [API] Fix task definition edit doesn't work | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Problem description: All versions have the problem that task definition changes do not take effect in the workflow and vice versa. There are several points as follows:
1、Modify the task definition without a predecessor task, but it is not available in the workflow.
2、Modify the task definition with a predecessor task, but it is not available in the workflow.
3、Switch the workflow version and modify the task definition, which is not available in the workflow.
### What you expected to happen
The modifications in the task definition should also take effect in the workflow
### How to reproduce
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15036 | https://github.com/apache/dolphinscheduler/pull/14801 | 688f84452da6e99ca43c650a2eb9528233d5d579 | ae847ba331ac6edec3c6b2e7013098bb274a5871 | "2023-10-16T09:10:48Z" | java | "2023-10-25T12:25:02Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,026 | ["docs/docs/zh/guide/resource/file-manage.md"] | [Doc][file-manage] content text error | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
<img width="1438" alt="image" src="https://github.com/apache/dolphinscheduler/assets/29291456/d0b5585d-4ac0-4197-841a-c9260d45214a">
### Documentation Links
https://dolphinscheduler.apache.org/zh-cn/docs/3.1.8/guide/resource/file-manage
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15026 | https://github.com/apache/dolphinscheduler/pull/15032 | a13ce27671f3b2cf41de107c9445fec48ddb7be2 | 06c3663e22e348d2a880dc8940be3e39cc4aefde | "2023-10-13T07:40:06Z" | java | "2023-10-17T09:15:41Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,023 | ["dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-email/src/main/java/org/apache/dolphinscheduler/plugin/alert/email/MailSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-pagerduty/src/main/java/org/apache/dolphinscheduler/plugin/alert/pagerduty/PagerDutySender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-webexteams/src/main/java/org/apache/dolphinscheduler/plugin/alert/webexteams/WebexMessage.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-webexteams/src/main/java/org/apache/dolphinscheduler/plugin/alert/webexteams/WebexTeamsSender.java"] | [Improvement][Alert] Alert plugin enhance fail message | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Alert plugin enhance fail message, user can see the error reason in db
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15023 | https://github.com/apache/dolphinscheduler/pull/15024 | 33084d281f303701b345051f306fb505f78a0152 | 154e1679f9e162ef04a4c4fe6d4b07f87122c546 | "2023-10-13T06:53:06Z" | java | "2023-10-16T05:13:45Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,017 | ["dolphinscheduler-ui/src/views/projects/workflow/definition/components/table-action.tsx", "dolphinscheduler-ui/src/views/projects/workflow/instance/components/table-action.tsx", "dolphinscheduler-ui/src/views/projects/workflow/instance/index.tsx", "dolphinscheduler-ui/src/views/resource/components/resource/table/table-action.tsx"] | [Improvement][workFlow] online,offline and delete Button, edge Popconfirm message does not take effect | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
online,offline and delete Button, edge Popconfirm message does not take effect
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15017 | https://github.com/apache/dolphinscheduler/pull/15018 | 1f67e68400661fb03bb111b25294065c8096d375 | d983e36ea4fedd391cbed78067b1861e3daf122f | "2023-10-12T07:27:55Z" | java | "2023-10-12T12:01:04Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,013 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/RetryUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/test/java/org/apache/dolphinscheduler/plugin/task/api/utils/RetryUtilsTest.java"] | [Bug] [dolphinscheduler-task-api] RetryUtils:The retryInterval variable is not correctly assigned! | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The retryInterval variable is not correctly assigned
### What you expected to happen
The retryInterval variable should be assigned retryPolicy.retryInterval;
long retryInterval = retryPolicy.retryInterval;
### How to reproduce
always
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15013 | https://github.com/apache/dolphinscheduler/pull/15014 | 8abb5e55b7f3ad12d4c33163927471bcbeab6c5d | d80a29c48cc5a29b0ef3888d6e2f6aa678742de3 | "2023-10-11T12:15:07Z" | java | "2024-01-25T07:07:11Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,009 | ["dolphinscheduler-dao/src/main/resources/sql/dolphinscheduler_h2.sql", "dolphinscheduler-dao/src/main/resources/sql/dolphinscheduler_mysql.sql", "dolphinscheduler-dao/src/main/resources/sql/dolphinscheduler_postgresql.sql", "dolphinscheduler-dao/src/main/resources/sql/upgrade/3.2.1_schema/mysql/dolphinscheduler_ddl.sql", "dolphinscheduler-dao/src/main/resources/sql/upgrade/3.2.1_schema/postgresql/dolphinscheduler_ddl.sql"] | [Improvement][Parameter] Change project parameter value to text | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Change project parameter value form varchar to text
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15009 | https://github.com/apache/dolphinscheduler/pull/15010 | f2d146665c78fedd09027ba624aa5b5180bc7f33 | b4cf1ccaac59093963ec943f32fd421c3730ada6 | "2023-10-11T02:20:20Z" | java | "2023-11-30T05:56:22Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 15,007 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/rpc/LogicITaskInstanceDispatchOperationFunction.java", "dolphinscheduler-worker/src/main/java/org/apache/dolphinscheduler/server/worker/runner/GlobalTaskInstanceDispatchQueueLooper.java"] | [Bug] [worker-server] task delay execution | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
start a task, task delay execution
### What you expected to happen
After submitting a task, it will run normally immediately
### How to reproduce
1.Start task ,Occasional appearance
2. Looking at the code, I found that the code logic did not consider this exception.
When there is an abnormality in the time zone under certain circumstances
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/15007 | https://github.com/apache/dolphinscheduler/pull/15012 | 23b2c8a532296caad987d296b8fcace62facce28 | d6835533243e692f4d23b7e6923b2bf4d748ee52 | "2023-10-11T02:12:04Z" | java | "2023-10-11T07:32:07Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,987 | ["dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/constants/DataSourceConstants.java", "dolphinscheduler-common/src/test/java/org/apache/dolphinscheduler/common/log/SensitiveDataConverterTest.java"] | [Improvement][Task] Mask password in task log | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Datasource password should better not visible in log.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14987 | https://github.com/apache/dolphinscheduler/pull/14988 | 629fced9efa0724463bcfe9410486d79af482a2a | 2a6559011757267c387174b030444427b1650929 | "2023-10-07T10:41:59Z" | java | "2023-10-08T06:54:45Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,971 | ["dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-api/src/main/java/org/apache/dolphinscheduler/alert/api/HttpServiceRetryStrategy.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-dingtalk/src/main/java/org/apache/dolphinscheduler/plugin/alert/dingtalk/DingTalkSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-feishu/src/main/java/org/apache/dolphinscheduler/plugin/alert/feishu/HttpRequestUtil.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-pagerduty/src/main/java/org/apache/dolphinscheduler/plugin/alert/pagerduty/PagerDutySender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-slack/src/main/java/org/apache/dolphinscheduler/plugin/alert/slack/SlackSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-telegram/src/main/java/org/apache/dolphinscheduler/plugin/alert/telegram/TelegramSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-webexteams/src/main/java/org/apache/dolphinscheduler/plugin/alert/webexteams/WebexTeamsSender.java", "dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-wechat/src/main/java/org/apache/dolphinscheduler/plugin/alert/wechat/WeChatSender.java"] | [Improvement][Alert] Webex and PagerDuty Alert plugin add retry logic | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Now alert plugins just run once, and when occur network issues will not retry, so add retry logic
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14971 | https://github.com/apache/dolphinscheduler/pull/14972 | 4fe41ac57f3684d54a438a688a103b82dbd13d87 | a866de1754bd81fca2c72e5beced4288700903d3 | "2023-09-27T09:18:15Z" | java | "2023-10-11T02:20:43Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,965 | ["dolphinscheduler-api/src/main/resources/logback-spring.xml"] | [Bug] [Api] Logback file STDOUT duplicate | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Error line
### What you expected to happen
Delete error duplicate config line
### How to reproduce
.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14965 | https://github.com/apache/dolphinscheduler/pull/14966 | 6de1e2c1b39da7031d790efa6f44d1aef4faa14c | 8cb765bdcb142526ff43a5dc06ce141f55d3374c | "2023-09-26T09:56:02Z" | java | "2023-09-26T12:19:43Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,963 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/shell/BaseLinuxShellInterceptorBuilder.java"] | [Bug] [Task] The error of using shell task to obtain Home variable in Ubuntu system | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The error of using shell task to obtain Home variable in Ubuntu system
### What you expected to happen
Get the Home variable normally
### How to reproduce
1.Configure DolphinScheduler Worker Server on ubuntu system
2.Add a new shell task, script: echo $HOME
3.Set up a tenant to execute. The print result is not the HOME directory of this tenant.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14963 | https://github.com/apache/dolphinscheduler/pull/14964 | 020092ed1e8328e76a27d06632337bb3e0324f5a | 6de1e2c1b39da7031d790efa6f44d1aef4faa14c | "2023-09-26T08:23:10Z" | java | "2023-09-26T09:18:38Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,951 | ["dolphinscheduler-ui/src/views/resource/components/resource/edit/index.tsx", "dolphinscheduler-ui/src/views/resource/components/resource/edit/use-edit.ts", "dolphinscheduler-ui/src/views/resource/components/resource/index.tsx", "dolphinscheduler-ui/src/views/resource/components/resource/table/use-table.ts"] | [Improvement][Resources Project] The details page does not return to the previous list page after returning to the list page | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
version 3.1.x 、3.2.x
**Current Problems**
When you come to the task or workflow list interface(Figure 1), click the task edit button on the specified page to enter the task details page(Figure 2). When you return, you will jump to the first page instead of the page where the original task is located(Figure 3). Very unfriendly to the user's experience.
When you come to the list interface of the resource file, click the edit button of the resource file on the specified page to enter the details page of the resource file. When you return or save, you will jump to the first page instead of the page where the original resource file is located. It is also very unfriendly to the user's experience.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14951 | https://github.com/apache/dolphinscheduler/pull/14954 | d983e36ea4fedd391cbed78067b1861e3daf122f | 166ef69066e682ee89d2b7e0ec45b0aecbdce864 | "2023-09-21T13:48:18Z" | java | "2023-10-13T03:07:33Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,928 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/RetryUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/test/java/org/apache/dolphinscheduler/plugin/task/api/utils/RetryUtilsTest.java"] | [Bug] [master server] retry task not work | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
After configuring retry, when it fails, the retry task will not be executed occasionally.
### What you expected to happen
After configuring retry, when it fails, the retry task will be executed.
### How to reproduce
occasionally
### Anything else
my version is 2.0.5
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14928 | https://github.com/apache/dolphinscheduler/pull/15014 | 8abb5e55b7f3ad12d4c33163927471bcbeab6c5d | d80a29c48cc5a29b0ef3888d6e2f6aa678742de3 | "2023-09-14T14:57:04Z" | java | "2024-01-25T07:07:11Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,918 | ["dolphinscheduler-dao/src/main/resources/sql/upgrade/3.2.0_schema/mysql/dolphinscheduler_ddl.sql", "dolphinscheduler-dao/src/main/resources/sql/upgrade/3.2.0_schema/postgresql/dolphinscheduler_ddl.sql"] | [Bug] [DDL] Missing ddl | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Missing ddl
### What you expected to happen
fix
### How to reproduce
fix
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14918 | https://github.com/apache/dolphinscheduler/pull/14921 | 6dcc26f52e9ea59057db25a44bc65ded65bc5dfd | e3482fbe5d8260f14cbe490f1533c373b7548e1c | "2023-09-14T06:36:43Z" | java | "2023-09-18T10:15:48Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,916 | ["dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/ProcessAlertContent.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/TaskAlertContent.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/alert/ProcessAlertManager.java"] | [Improvement][dolphinscheduler-alert] alert message contains the taskPriority | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
This improvement hopes to alert message contains the taskPriority
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14916 | https://github.com/apache/dolphinscheduler/pull/14919 | f6a6794289ff984227548ff74affcf83fbced289 | 6dcc26f52e9ea59057db25a44bc65ded65bc5dfd | "2023-09-14T01:58:27Z" | java | "2023-09-15T09:30:25Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,895 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/LoggerServiceImpl.java"] | [Bug] [API] Keep printing null if task log file not exist | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
If we manually delete log file on Worker server, then we query logs and it will keep printing null log in UI page. And it will also print thousands of rows backend logs in a moment.
The reason is response of queryLog contains `data.message` "null" (String value), and will send another request to rolling view logs . It should directly return null to represent no more logs.
<img width="782" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/6447cb22-1488-494b-ad80-34fa468e667e">
### What you expected to happen
Do not send requests continuously.
### How to reproduce
Easy to reproduce, just delete a task log file and then query it.
### Anything else
Test in dev, not sure if the bug exists in release version.
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14895 | https://github.com/apache/dolphinscheduler/pull/14912 | 9083f9d0e0be6dab488b049aaa51f3f447edc272 | 2f2884fd6b052d7536ac984de4df2d24a7736a2f | "2023-09-11T14:32:30Z" | java | "2023-09-19T10:29:33Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,894 | ["dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/ProcessAlertContent.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/alert/ProcessAlertManager.java", "dolphinscheduler-service/src/test/java/org/apache/dolphinscheduler/service/alert/ProcessAlertManagerTest.java"] | [Improvement][dolphinscheduler-alert] alert message contains the operator of the alerted task | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Currently, the alert message only have the administrator user of project.
If there are different people creating tasks in the same project. If a task is alerted, the alert message will only contain information about the administrator of the project, but not the operator of the alerted task.
This improvement hopes to alert message contains the operator of the alerted task.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14894 | https://github.com/apache/dolphinscheduler/pull/14910 | ab29ae77c134f0909756ce2ff56d962502cfe2fa | 4b5eb1a2bb07a75c8430271af0aef38e013f73a8 | "2023-09-11T11:19:15Z" | java | "2023-09-25T02:50:28Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,885 | ["dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-all/pom.xml", "pom.xml"] | [Bug] mvn package error, coun't find `spotless` path | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Using `mvn install` to package and install a module is invalid.
### What you expected to happen
Individual modules can be packaged correctly.
### How to reproduce
Use `Idea Intellij` to open ds and then use the maven GUI on the right to package an independent module such as `ds-dao`. This error occurs.
### Anything else
It seems that there is a problem with the path setting of the formatted file of the spotless plugin. The path relative to the ds root directory should be used.
`<file>${maven.multiModuleProjectDirectory}/style/eclipse.importorder</file>`
rather than
`<file>style/eclipse.importorder</file>`
After fix like this, it works normally.
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14885 | https://github.com/apache/dolphinscheduler/pull/14889 | 28788c7df69f8ae19ad565b548da643dbd52e825 | 8f16fd797596022e9f084dc1ffa39546597330d5 | "2023-09-09T14:27:19Z" | java | "2023-10-17T11:20:23Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,870 | ["dolphinscheduler-ui/src/views/projects/workflow/components/dag/use-custom-cell-builder.ts", "dolphinscheduler-ui/src/views/projects/workflow/components/dag/use-task-edit.ts", "dolphinscheduler-ui/src/views/projects/workflow/components/dag/x6-style.scss"] | [Improvement][UI] Optimize task disable node style in dark theme | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
when the task node run flag in `prohibition execution` state, it is difficult to distinguish from the normal state in dark theme.
light theme mode is clear
<img width="478" alt="Screenshot 2023-09-07 at 13 13 17" src="https://github.com/apache/dolphinscheduler/assets/45848815/8e0d2ff9-cf42-4bb2-86d8-20db5683cfd8">
dark theme mode is not clear
<img width="445" alt="Screenshot 2023-09-07 at 13 14 05" src="https://github.com/apache/dolphinscheduler/assets/45848815/ae396a01-884d-4b90-a09c-54409bda3aa9">
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14870 | https://github.com/apache/dolphinscheduler/pull/14871 | f3a4842bf6704568a222a4030b6c932c6fac1eba | 70e384c9fca9e7caf9a079b93c60ad5a379251b8 | "2023-09-07T05:22:27Z" | java | "2023-09-07T23:39:05Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,869 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/AbstractTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-sql/src/test/java/org/apache/dolphinscheduler/plugin/task/sql/SqlTaskTest.java"] | [Bug] [API] Global and local parameters are not replaced with XX value in SQL/SHELL components | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
1、create process ”test0907“ && add shell components ”echo ${dt}"
2、add global parameter： name：“dt”，value：“$[yyyy-MM-dd]” && save process
3、run this process，view logs after finished
### What you expected to happen
Global and local parameters can be replaced correctly.
### How to reproduce
eg. "what happened"
### Anything else
_No response_
### Version
3.2.0-prepare
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14869 | https://github.com/apache/dolphinscheduler/pull/14926 | 73e846d03ebb499cf71d08267ca82c727ae8f21e | f6a6794289ff984227548ff74affcf83fbced289 | "2023-09-07T00:53:06Z" | java | "2023-09-15T02:31:14Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,864 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/enums/Status.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/WorkerGroupServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/WorkerGroupServiceTest.java"] | [Improvement][UI] Need to check if the worker group has been used by any tasks or schedulers when users delete or rename it. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
At present, the DS has used the name of worker group as the unique identifier. And all of tasks and schedulers use its name in their settings. Once it's deleted or renamed, its dependent tasks won't be able to work well. So when users delete or rename a worker group, it's supposed to check if it has been used by any tasks or schedulers.
This issue is related to #11805.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14864 | https://github.com/apache/dolphinscheduler/pull/14893 | e7c579d8f1bcb7f4e91053bb23c6bcf743e1d050 | a070aa93a72c6252b49514e66bb3b05291deacb7 | "2023-09-06T06:09:59Z" | java | "2023-09-13T02:34:59Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,861 | ["dolphinscheduler-ui/src/views/projects/workflow/components/dag/use-task-edit.ts"] | [Bug] [UI] New tasks with the flag normal show a grey color | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
- Due #14837
New tasks with the flag normal show a grey color
<img width="625" alt="image" src="https://github.com/apache/dolphinscheduler/assets/20885366/256c039f-7a7b-4036-ac78-a711c820841f">
<img width="343" alt="image" src="https://github.com/apache/dolphinscheduler/assets/20885366/51d527f5-af08-4c2d-9fb9-6c6c7b9bf42a">
### What you expected to happen
Show #ffffff
### How to reproduce
New a task
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14861 | https://github.com/apache/dolphinscheduler/pull/14862 | 11c8e0bdf1f3c22b51333b928e2f480f3312cf27 | 89a55de0706be0ea628fc7acd163240436c442e9 | "2023-09-06T03:23:05Z" | java | "2023-09-07T02:12:44Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,835 | ["dolphinscheduler-ui/src/views/projects/workflow/components/dag/use-cell-update.ts", "dolphinscheduler-ui/src/views/projects/workflow/components/dag/use-task-edit.ts"] | [Improvement][UI] After switching the run flag of a task and saving it its task node can't change the color immediately. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
After switching the run flag of a task and saving it its task node can't change the color immediately.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14835 | https://github.com/apache/dolphinscheduler/pull/14837 | 7ae4fb378779077c75cd6411ef8e3b68f232bd84 | 168a3930faa6da24b4a7b1852e8b89a48350d132 | "2023-08-30T07:48:40Z" | java | "2023-09-01T01:01:16Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,830 | ["dolphinscheduler-storage-plugin/dolphinscheduler-storage-s3/src/main/java/org/apache/dolphinscheduler/plugin/storage/s3/S3StorageOperator.java"] | [Improvement][dolphinscheduler-storage-s3] Allow AWS S3 compatible Object storage using custom named regions | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Version: 3.1.8
When I use a third-party AWS S3 compatible Object storage and use a custom region name, the AWS client will fail to initialize and report an error as follows:
By checking the source code, it was found that 3.2.0 and dev have the same issue, that is, checking whether the configured `region` exists in the official S3 SDK. If not, an error will be reported
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14830 | https://github.com/apache/dolphinscheduler/pull/14831 | 82eeeec750395d95e5cc788fd7737ce44d245484 | 6e5870d71197341a9b2a3655932de2ed24bcfb36 | "2023-08-30T01:42:32Z" | java | "2023-08-31T09:53:30Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,811 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/LoginController.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java"] | [Bug] [api] When using Casdoor SSO, ldap, OAuth2 to log in, the tenant of the currently logged in user is not specified | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When using Casdoor SSO, ldap, or OAuth2 to log in, if the user is logging in for the first time, the tenant is not specified when creating a new user in the t_ds_user table, and the default is 0. When logging in, the tenant will be checked when the resource interface is obtained, and the tenant of the current login user is not specified. question
### What you expected to happen
### How to reproduce
using Casdoor SSO, ldap, or OAuth2 to log in
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14811 | https://github.com/apache/dolphinscheduler/pull/14812 | b12df72a0c59e3552dcb9af9971a897f725d602a | 5062aa12dae1c725d415205e360a9b59a23f9a6e | "2023-08-25T02:00:18Z" | java | "2023-09-07T11:56:38Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,802 | ["docs/docs/en/architecture/configuration.md", "docs/docs/en/guide/security/authentication-type.md", "docs/docs/zh/architecture/configuration.md", "docs/docs/zh/guide/security/authentication-type.md", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/security/impl/sso/CasdoorAuthenticator.java", "dolphinscheduler-api/src/main/resources/application.yaml", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/security/impl/sso/CasdoorAuthenticatorTest.java", "dolphinscheduler-api/src/test/resources/application.yaml", "dolphinscheduler-standalone-server/src/main/resources/application.yaml"] | [Feature][API] Add admin user configuration when Casdoor SSO is added | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Add the admin user configuration when Casdoor SSO is specified, similar to the ldap.user.admin configuration parameter when using ldap login
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14802 | https://github.com/apache/dolphinscheduler/pull/14814 | 46c0eb48c6e4729b953df2523cac16b5be3887a5 | adf49fd23f6bcafa1ded60da7bc8bdf1a3575fd3 | "2023-08-24T06:19:53Z" | java | "2023-09-04T05:25:40Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,790 | ["dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-rules.ts"] | [Improvement][UI] The data quality task, keyword filtering not supported | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
When i create a data quality task, the data quality rules cannot to filter by keywords. My ds version is 3.1.7
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14790 | https://github.com/apache/dolphinscheduler/pull/14792 | 613bcc3b5e7e9bda1cc8b1530cedbefd11489a0b | 034e99f5a9f6f3877ca974603f245160088a6d30 | "2023-08-22T07:57:34Z" | java | "2023-09-12T04:35:57Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,788 | ["dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-dependent.ts"] | [Improvement][UI] The task name of dependent node, keyword filtering not supported | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
When i create a dependent task, the task name cannot to filter by keywords. My ds version is 3.1.7
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14788 | https://github.com/apache/dolphinscheduler/pull/14791 | 034e99f5a9f6f3877ca974603f245160088a6d30 | 121c981a5d28e82d10f74427d3cbf5e4b100d29a | "2023-08-22T07:49:07Z" | java | "2023-09-12T07:11:00Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,734 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [Master] Environment configuration lost during fault tolerance | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
If the worker hangs up first, and then the master hangs up again, the environment configuration will be lost when the task is fault-tolerant
### What you expected to happen
empty
### How to reproduce
empty
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14734 | https://github.com/apache/dolphinscheduler/pull/14735 | 93b0283dfe916a091cf24556eb2b03e6a8732ef5 | 8e64026e93ed5451ade1d16549290028cc3fb0d9 | "2023-08-11T05:49:16Z" | java | "2023-08-11T06:35:31Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,729 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-flink/src/main/java/org/apache/dolphinscheduler/plugin/task/flink/FlinkArgsUtils.java"] | [Bug] [flink task] problem with the command generated by the flink task | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
1. The determinedYarnQueue method in the FlinkArgsUtils class and the switch statement of the doAddQueue method lack a break, resulting in problems with the generated flink commands
2. The result of my experiment is that if you want to submit to the specified queue, you need to put the -Dyarn or -yqu parameter before -c, so you need to put the determinedYarnQueue method on line 284 before line 261
### What you expected to happen
Generate the correct flink submission task command and submit it to the specified yarn queue
### How to reproduce
Try to submit the flink task to the specified yarn queue under version 3.1.8
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14729 | https://github.com/apache/dolphinscheduler/pull/14902 | b3036487524889934457f605ce92cece74d5efc6 | e748c2eb9a8e0e8a365d58a91b5c24db837c8667 | "2023-08-10T06:33:22Z" | java | "2023-09-21T10:46:14Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,721 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/k8s/impl/K8sTaskExecutor.java"] | [Bug] [K8S Task] Handle job delete event when user manually delete the job in k8s cluster | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Run a K8S task, if the pod is pending for some reasons (such as unmatchable node label), and then user manually delete k8s job in the cluster via command line - `kubectl delete job`. Now, DS can not handle job delete event, and job will keep running.
### What you expected to happen
We should better handle this delete action and set the task status to failure, directly delete job may because of some unexpected operation.
### How to reproduce
Ditto.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14721 | https://github.com/apache/dolphinscheduler/pull/14722 | 8e64026e93ed5451ade1d16549290028cc3fb0d9 | cb55476235c6a5d5fddfa24f5944e2cc8aeae390 | "2023-08-08T15:29:19Z" | java | "2023-08-11T09:15:07Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,715 | ["dolphinscheduler-storage-plugin/dolphinscheduler-storage-hdfs/src/main/java/org/apache/dolphinscheduler/plugin/storage/hdfs/LocalStorageOperatorFactory.java"] | [Bug] [Resource Center] Modify default fs of local storage plugin | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
<img width="1786" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/ee945851-0d33-41f9-a88c-6a7884ded44b">
### What you expected to happen
<img width="1739" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/aa288691-d050-415d-a3f6-6526c44f844c">
### How to reproduce
Use local storage plugin and enter resource center.
### Anything else
For UI display, we use full name without prefix(base dir) to generate breadcrumb navigator. Thus, we should set the prefix to `file:/`, because local storage plugin reuse `HdfsStorageOperator`, when we list all files, actually we get files under this path: `Path filePath = new Path(path);`. `new Path` will change `file:///` to `file:/`, so we should directly use `file:/` as defaultFS.
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14715 | https://github.com/apache/dolphinscheduler/pull/14716 | 27745a8a8470c27d3c6d78a19195901a72980446 | 2314b67870ef8523f7b783dd21f23ee6acbaca16 | "2023-08-07T15:10:27Z" | java | "2023-08-10T11:15:09Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,696 | ["dolphinscheduler-standalone-server/src/main/bin/start.sh"] | [Bug] [Startup scripts] /bin/java command Argument list too long | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When the deployment path is too long, below errors may occur.
`/bin/java command Argument list too long.`
### What you expected to happen
Successfully running.
### How to reproduce
eg: /data/master/dolphinscheduler/ds_dev/test/standalone-server
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14696 | https://github.com/apache/dolphinscheduler/pull/14697 | a5f5aacb5dc58dc05cd7c98c6614e44e2f4f6140 | 85f6a6e73cc84f757f16635ac91bf776542f21f7 | "2023-08-03T08:53:36Z" | java | "2023-08-03T11:04:00Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,685 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/shell/sh/ShShellInterceptorBuilder.java"] | [Bug] [Task] Remove override method k8sConfigYaml in ShShellInterceptorBuilder | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Set `shell.interceptor.type` to `sh`, run Spark on K8S task, do not set `k8sConfigYaml` in `ShShellInterceptorBuilder`, because there's an override method in `ShShellInterceptorBuilder` which directly return null.
### What you expected to happen
Remove this override method.
### How to reproduce
Ditto.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14685 | https://github.com/apache/dolphinscheduler/pull/14682 | 139f23040a0abc14a23872d4426196d558044c61 | 5ec9085113c989c06a23d0e6820627b147dad15e | "2023-08-02T03:00:49Z" | java | "2023-08-02T10:01:34Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,683 | ["docs/docs/en/guide/upgrade/incompatible.md", "docs/docs/zh/guide/upgrade/incompatible.md", "dolphinscheduler-bom/pom.xml"] | [Bug] [pom] MySQL stores null but the driver returns 0 | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
MySQL stores null but the driver returns 0.
> ResultSetImpl.getObject(), when autoboxing a value of a primitive type retrieved from a column, returned a non-null object when the retrieved value was null. (Bug #29446100, Bug #94533)
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-17.html
This is a driver bug that needs to be resolved through upgrade
### What you expected to happen
refer What happened
### How to reproduce
refer What happened
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14683 | https://github.com/apache/dolphinscheduler/pull/14684 | 57b9da145ec65cc876acb1e558b58ffc2ccc753f | 4bae7b1ae24e4437b844b701d2524c45ad053c97 | "2023-08-02T02:50:03Z" | java | "2023-08-04T02:51:15Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,675 | ["dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/mapper/AlertSendStatusMapper.java", "dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/AlertSendStatusMapper.xml"] | [Bug] [Alert] batchInsert execption | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
1. Configure an alert instance on the UI, select the Feishu type, and configure the alert instance.
2. Configure an alert group and select the above alert instance.
3. Configure a scheduled task, select to send notifications for both success and failure in the notification strategy, and select the above configured alert group.
Error message: When waiting for the scheduled task to execute, the following error message will be displayed on the alert server:
```
[ERROR] 2023-07-31 19:54:09.360 +0800 org.apache.dolphinscheduler.alert.service.AlertBootstrapService:[90] - Alert sender thread meet an exception
org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.binding.BindingException: Parameter 'alertSendStatuses' not found. Available parameters are [arg0, collection, list]
at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:96)
at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:441)
at com.sun.proxy.$Proxy133.insert(Unknown Source)
at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:272)
at com.baomidou.mybatisplus.core.override.MybatisMapperMethod.execute(MybatisMapperMethod.java:59)
at com.baomidou.mybatisplus.core.override.MybatisMapperProxy$PlainMethodInvoker.invoke(MybatisMapperProxy.java:148)
at com.baomidou.mybatisplus.core.override.MybatisMapperProxy.invoke(MybatisMapperProxy.java:89)
at com.sun.proxy.$Proxy137.batchInsert(Unknown Source)
at org.apache.dolphinscheduler.dao.AlertDao.insertAlertSendStatus(AlertDao.java:156)
at org.apache.dolphinscheduler.alert.service.AlertBootstrapService.send(AlertBootstrapService.java:156)
at org.apache.dolphinscheduler.alert.service.AlertBootstrapService.run(AlertBootstrapService.java:88)
Caused by: org.apache.ibatis.binding.BindingException: Parameter 'alertSendStatuses' not found. Available parameters are [arg0, collection, list]
at org.apache.ibatis.binding.MapperMethod$ParamMap.get(MapperMethod.java:212)
at org.apache.ibatis.scripting.xmltags.DynamicContext$ContextAccessor.getProperty(DynamicContext.java:120)
at org.apache.ibatis.ognl.OgnlRuntime.getProperty(OgnlRuntime.java:3341)
at org.apache.ibatis.ognl.ASTProperty.getValueBody(ASTProperty.java:121)
at org.apache.ibatis.ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:212)
at org.apache.ibatis.ognl.SimpleNode.getValue(SimpleNode.java:258)
at org.apache.ibatis.ognl.Ognl.getValue(Ognl.java:586)
at org.apache.ibatis.ognl.Ognl.getValue(Ognl.java:550)
```
### What you expected to happen
no error
### How to reproduce
as mentioned above
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14675 | https://github.com/apache/dolphinscheduler/pull/14676 | b391b74df4baf7b6f90df79df584e391ee799279 | 37ecd262ee9a2228f0daf84e336dcfdd6f2ae9ad | "2023-08-01T02:40:36Z" | java | "2023-08-01T05:54:00Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,658 | ["dolphinscheduler-registry/dolphinscheduler-registry-plugins/dolphinscheduler-registry-etcd/src/main/java/org/apache/dolphinscheduler/plugin/registry/etcd/EtcdRegistry.java"] | [Improvement][etcd] Distinguish between add and update by using pre kv | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
When using ETCD as the registry, each heartbeat task is considered an add event. This can lead to some misunderstandings. Add and update should be distinguished by whether there is a pre kv
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14658 | https://github.com/apache/dolphinscheduler/pull/14659 | d223d654ccfbf5621c4faeed1b7fe45715bf5a6b | 3148dba7a52f7917ca5c8eecd01157ab5b62c585 | "2023-07-29T02:26:36Z" | java | "2023-08-28T01:28:52Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,656 | ["deploy/kubernetes/dolphinscheduler/templates/deployment-dolphinscheduler-alert.yaml", "deploy/kubernetes/dolphinscheduler/templates/deployment-dolphinscheduler-api.yaml", "deploy/kubernetes/dolphinscheduler/templates/statefulset-dolphinscheduler-master.yaml", "deploy/kubernetes/dolphinscheduler/templates/statefulset-dolphinscheduler-worker.yaml", "deploy/kubernetes/dolphinscheduler/values.yaml"] | [Improvement][helm] configmap changes automatically trigger restarts | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
After modifying `conf.common` via Helm, a manual restart of DolphinScheduler is required. It is desired to have an automatic restart triggered instead.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14656 | https://github.com/apache/dolphinscheduler/pull/14657 | 420bcd69a6360631052e6bc352bdc2ad644962fa | 11d1df2f326a426b6f62aea2a45dbce5722e7b5b | "2023-07-28T12:11:27Z" | java | "2023-08-09T02:30:20Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,648 | ["dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-k8s.ts"] | [Improvement][UI] Image pull policy in the K8S task provides default values | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
The Image Pull Policy is a required field in the current K8S task UI, but no default value is provided. Providing a default value would improve the user experience. In most cases, IfNotPresent is sufficient.
ref:[K8S images](https://kubernetes.io/docs/concepts/containers/images/#updating-images)
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14648 | https://github.com/apache/dolphinscheduler/pull/14650 | d87a0d831c7bbf768c2c80ab1e0020c3ebc5f4aa | 150d9e04b0675e3d4bee6000a742a0e54846472e | "2023-07-28T01:38:02Z" | java | "2023-07-29T11:56:19Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,646 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/ProcessUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/test/java/org/apache/dolphinscheduler/plugin/task/api/utils/ProcessUtilsTest.java"] | [Bug] [Worker] Match wrong pid on linux server | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
If you deploy DS on linux server, cancel process instance, then it's possible to get error log:
```
[ERROR] 2023-07-27 23:14:54.887 +0800 org.apache.dolphinscheduler.server.worker.processor.WorkerTaskKillProcessor:[196] - kill task error
org.apache.dolphinscheduler.common.shell.AbstractShell$ExitCodeException: kill: (26483): Operation not permitted
kill: (558): No such process
kill: (1493): No such process
```
### What you expected to happen
No error log.
### How to reproduce
Ditto.
### Anything else
That is because in `ProcessUtils.getPidsStr`, only match pids on macos and windows.
```java
if (SystemUtils.IS_OS_MAC) {
String pids = OSUtils.exeCmd(String.format("%s -sp %d", TaskConstants.PSTREE, processId));
if (null != pids) {
mat = MACPATTERN.matcher(pids);
}
} else {
String pids = OSUtils.exeCmd(String.format("%s -p %d", TaskConstants.PSTREE, processId));
mat = WINDOWSATTERN.matcher(pids);
}
```
If run on linux server, will get pids string like: `sudo(6279)---558_1497.sh(6282)---sleep(6354)`, but if use windows matcher, it will match "6279 558 1497 6282 6354", expected matching results is "6279 6282 6354".
### Version
dev
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14646 | https://github.com/apache/dolphinscheduler/pull/14652 | f7ba26f030608993772d97b0d0f1abe0a288d985 | b3af374fe600c0fda9ea1ab2247921388f559114 | "2023-07-27T15:43:42Z" | java | "2023-08-17T11:17:16Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,627 | ["dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-child-node.ts"] | [Improvement] [UI] There are too many child node in sub_process, it cannot to filter by keywords | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When i create a sub_process task, there are too many child node in sub_process, it cannot to filter by keywords. My ds version is 3.1.7
### What you expected to happen
Child node can filter by keywords
### How to reproduce
When i create a sub_process task, there are too many child node in sub_process, it cannot to filter by keywords. My ds version is 3.1.7
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14627 | https://github.com/apache/dolphinscheduler/pull/14770 | a491e3a849ce7e07e9be701470fce8fc69c1eea0 | 502bd36fde3cc57e6119d8044e8a4ea5f27a30a0 | "2023-07-24T03:51:03Z" | java | "2023-08-20T06:30:47Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,603 | ["dolphinscheduler-ui/src/views/security/user-manage/components/use-user-detail.ts"] | [Bug] [ui] Phone number verification failed | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
On the role creation page, when the phone number starts with 19, the phone number verification will fail
### What you expected to happen
Modify the verification rules to support mobile phone numbers starting with 19
### How to reproduce
Role management, create role function
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14603 | https://github.com/apache/dolphinscheduler/pull/14604 | 3d033da55d44a9c5f6a6eaae86602f58843288d1 | cbfb1cbffb84d717603fe36cc7a5bc03801d40f6 | "2023-07-20T08:41:31Z" | java | "2023-07-20T12:39:54Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,601 | ["dolphinscheduler-ui/src/views/projects/task/components/node/tasks/use-datasync.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/tasks/use-dms.ts"] | [Bug] [UI] There're something wrong with choosing environment on the task form of both types of DMS and DATASYNC. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
After choosing an environment and saving the task that is a type of DMS or DATASYNC, if you open the task form one more time the value of environment on the task form will possibly change.
### What you expected to happen
I expect to fix this issue.
### How to reproduce
1、First of all, create a workflow and a task that is a type of DMS or DATASYNC.
2、Choose an environment on the task form and save it.
3、Open that again and cancel the option of environment, and then save it.
4、Open it one more time, you will see the value of environment has a option.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14601 | https://github.com/apache/dolphinscheduler/pull/14605 | cbd354d134ca32194c91c85f8ea3ffe615bd5536 | fc65c185dc52d0d390be002c97d69f3b9001ea1f | "2023-07-20T08:28:30Z" | java | "2023-07-20T14:27:28Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,593 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/k8s/K8sClientService.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/K8SNamespaceServiceImpl.java"] | [Improvement][K8S] Disable delete namespaces in the K8S cluster | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Managing namespaces in K8S is a critical task, and deleting a namespace can have severe consequences, especially in a production-level K8S cluster. Typically, such operations are intercepted by a policy engine at the K8S Cluster to prevent accidental deletion of namespaces. If a namespace is deleted in the DS, it can cause errors in the DS.
I recommended to remove the logic that cascades the deletion of the namespace in the K8S cluster.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14593 | https://github.com/apache/dolphinscheduler/pull/14597 | fc65c185dc52d0d390be002c97d69f3b9001ea1f | 1e3132741855e819f0739da922377538423328ec | "2023-07-20T02:39:31Z" | java | "2023-07-21T02:28:20Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,587 | ["dolphinscheduler-ui/src/views/projects/preference/components/use-alert-group.ts", "dolphinscheduler-ui/src/views/projects/preference/components/use-tenant.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-environment-name.ts"] | [Improvement][UI] Improve the environment component. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
When refreshing the page of project preferences there're something wrong with the environment component.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14587 | https://github.com/apache/dolphinscheduler/pull/14588 | af2986eca1b5b3a4007fc8eadd8b290a5db9bd2b | 50386d622c68c3984e77c9243ce945cec0df27fd | "2023-07-19T10:02:35Z" | java | "2023-07-19T10:46:46Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,580 | ["dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProjectParameterMapper.xml"] | [Improvement][Parameter] Improve the order of project parameter | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Improve the order of project parameter
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14580 | https://github.com/apache/dolphinscheduler/pull/14581 | 2b99451ccdbb5b2ba0993db49039d4fc48fa0bc4 | 79cf785ecab95223cab37f0c448d9913ce14a5e8 | "2023-07-19T05:06:33Z" | java | "2023-07-27T10:20:36Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,570 | ["dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/constants/Constants.java", "dolphinscheduler-common/src/test/java/org/apache/dolphinscheduler/common/log/SensitiveDataConverterTest.java", "dolphinscheduler-worker/src/main/java/org/apache/dolphinscheduler/server/worker/runner/WorkerTaskExecuteRunnable.java"] | [Improvement][Task] Mask configYaml in task log for non-admin users | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Kubernetes cluster's configYaml should better not visible in log.
<img width="645" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/5025ae9d-21e3-404a-9ac0-7b792801c213">
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14570 | https://github.com/apache/dolphinscheduler/pull/14571 | 5a6f1c88a345a752cec11b574ac39d241961b838 | 9d10de6efa2b0fa610ae1d53646a38ad58254a45 | "2023-07-17T11:45:10Z" | java | "2023-07-18T07:02:20Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,566 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java", "dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessServiceImpl.java"] | [Bug] [dolphinscheduler-master] SERIAL_WAIT command_param does not replace global_params, rendering the parameters passed via the API ineffective | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When I run multiple instances of the same workflow using the API and the execution strategy of the workflow definition is set to serial wait, the state of the workflow instances changes from "state":"SERIAL_WAIT","desc":"wait by serial_wait strategy" to "state":"RUNNING_EXECUTION","desc":"recover serial wait". In this case, the start params passed in through the API does not replace the global_params, which results in the parameters passed through the API becoming ineffective.
API URL: projects/{projectCode}/executors/start-process-instance
### What you expected to happen
The parameters passed through the API should properly replace the global_params.
### How to reproduce
Running multiple instances at once through API.
### Anything else
I rapidly ran multiple instances of the same workflow through the API with the execution policy established as serial waiting. In theory, these instances should execute sequentially. However, I've observed that some instances are executing simultaneously instead of following the expected waiting sequence.
### Version
3.1.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14566 | https://github.com/apache/dolphinscheduler/pull/14606 | 164154488a96300c0fc475f1d027e96ae1a9f809 | 4a80e3a0212cb83d072e77daa1e8cc8d65914241 | "2023-07-17T03:28:17Z" | java | "2023-07-25T05:36:35Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,556 | ["deploy/kubernetes/dolphinscheduler/templates/configmap.yaml", "deploy/kubernetes/dolphinscheduler/templates/deployment-dolphinscheduler-api.yaml", "deploy/kubernetes/dolphinscheduler/values.yaml", "docs/docs/en/guide/installation/kubernetes.md", "docs/docs/zh/guide/installation/kubernetes.md"] | [Feature][UI] shows supported task types on the front-end UI | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
At present, dolphinscheduler supports 30+ task types, but in fact, to use specific types of tasks, the administrator needs to configure the corresponding environment, such as hadoop spark and so on. However, it is often not possible to use all types in a real-world scenario. So is there a configuration item that shows supported task types on the `create task` page? This is more user friendly and does not incorrectly use unsupported task types.
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14556 | https://github.com/apache/dolphinscheduler/pull/15179 | 2b4edb3815035e75cd4189ebb9e81be6eee7085b | 2f2825784a0de770e746e9cb6b78bf1ce8811631 | "2023-07-14T09:39:48Z" | java | "2023-11-19T07:15:10Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,546 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-seatunnel/src/main/java/org/apache/dolphinscheduler/plugin/task/seatunnel/spark/SeatunnelSparkTask.java"] | [Bug] [Task Plugin] seatunnel unable submit spark job to spark:// | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When using the seatunel engine to submit Spark jobs, selecting Spark as the master did not concatenate the master address in the generated job submission script, resulting in job failure
it generated a script like this:
```
[INFO] 2023-07-14 00:39:14.376 +0000 - SeaTunnel task command: ${SEATUNNEL_HOME}/bin/start-seatunnel-spark-3-connector-v2.sh --config /tmp/dolphinscheduler/exec/process/root/10215811485920/10215863853024_2/9/9/seatunnel_9_9.conf --deploy-mode client --master spark:// sparkhost:port
```
and report this exception:
```
23/07/14 08:39:18 ERROR SparkContext: Error initializing SparkContext.
org.apache.spark.SparkException: Invalid master URL: spark://
at org.apache.spark.util.Utils$.extractHostPortFromSparkUrl(Utils.scala:2551)
at org.apache.spark.rpc.RpcAddress$.fromSparkURL(RpcAddress.scala:47)
at org.apache.spark.deploy.client.StandaloneAppClient.$anonfun$masterRpcAddresses$1(StandaloneAppClient.scala:53)
at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:286)
at scala.collection.IndexedSeqOptimized.foreach(IndexedSeqOptimized.scala:36)
at scala.collection.IndexedSeqOptimized.foreach$(IndexedSeqOptimized.scala:33)
at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:198)
at scala.collection.TraversableLike.map(TraversableLike.scala:286)
at scala.collection.TraversableLike.map$(TraversableLike.scala:279)
at scala.collection.mutable.ArrayOps$ofRef.map(ArrayOps.scala:198)
at org.apache.spark.deploy.client.StandaloneAppClient.<init>(StandaloneAppClient.scala:53)
at org.apache.spark.scheduler.cluster.StandaloneSchedulerBackend.start(StandaloneSchedulerBackend.scala:123)
at org.apache.spark.scheduler.TaskSchedulerImpl.start(TaskSchedulerImpl.scala:222)
at org.apache.spark.SparkContext.<init>(SparkContext.scala:595)
at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2714)
at org.apache.spark.sql.SparkSession$Builder.$anonfun$getOrCreate$2(SparkSession.scala:953)
at scala.Option.getOrElse(Option.scala:189)
at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:947)
at org.apache.seatunnel.core.starter.spark.execution.SparkRuntimeEnvironment.prepare(SparkRuntimeEnvironment.java:113)
at org.apache.seatunnel.core.starter.spark.execution.SparkRuntimeEnvironment.prepare(SparkRuntimeEnvironment.java:38)
at org.apache.seatunnel.core.starter.execution.RuntimeEnvironment.initialize(RuntimeEnvironment.java:48)
at org.apache.seatunnel.core.starter.spark.execution.SparkRuntimeEnvironment.<init>(SparkRuntimeEnvironment.java:60)
at org.apache.seatunnel.core.starter.spark.execution.SparkRuntimeEnvironment.getInstance(SparkRuntimeEnvironment.java:173)
at org.apache.seatunnel.core.starter.spark.execution.SparkExecution.<init>(SparkExecution.java:50)
at org.apache.seatunnel.core.starter.spark.command.SparkTaskExecuteCommand.execute(SparkTaskExecuteCommand.java:59)
at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40)
at org.apache.seatunnel.core.starter.spark.SeaTunnelSpark.main(SeaTunnelSpark.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.spark.deploy.JavaMainApplication.start(SparkApplication.scala:52)
at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:958)
at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:180)
at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:203)
at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:90)
at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:1046)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:1055)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Caused by: java.net.URISyntaxException: Expected authority at index 8: spark://
at java.net.URI$Parser.fail(URI.java:2847)
at java.net.URI$Parser.failExpecting(URI.java:2853)
at java.net.URI$Parser.parseHierarchical(URI.java:3101)
at java.net.URI$Parser.parse(URI.java:3052)
at java.net.URI.<init>(URI.java:588)
at org.apache.spark.util.Utils$.extractHostPortFromSparkUrl(Utils.scala:2536)
... 38 more
```
### What you expected to happen
There should be no spaces in the master address, like this
```
--master spark://sparkhost:port
```
### How to reproduce
the code of generating master args in org.apache.dolphinscheduler.plugin.task.seatunnel.spark.SeatunnelSparkTask: buildOptions() needs to be modified
if master is spark or mesos, the master command needs to be concatenated with the url
like this
```
args.add(MASTER_OPTIONS);
if (MasterTypeEnum.SPARK.equals(master) || MasterTypeEnum.MESOS.equals(master)) {
args.add(master.getCommand() + seatunnelParameters.getMasterUrl());
} else {
args.add(master.getCommand());
}
```
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14546 | https://github.com/apache/dolphinscheduler/pull/14617 | 298b8ccf5a263e875568ce124b765b4789fa8061 | 9083f9d0e0be6dab488b049aaa51f3f447edc272 | "2023-07-14T01:17:45Z" | java | "2023-09-19T05:23:27Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,543 | [".github/workflows/api-test.yml", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/cases/ProcessInstanceAPITest.java", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/pages/workflow/ProcessInstancePage.java"] | [Improvement][API Test] Add api tests for process instance | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
* Add api tests for process instance.
* Cover important ones, not every one.
* part of #10411
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14543 | https://github.com/apache/dolphinscheduler/pull/14514 | b5d88f2a6fbcb333c533bb0e53b6cb8671e7cec0 | 8020c1539c6788841d36c5b3de0df38eca3b0aa3 | "2023-07-13T12:04:21Z" | java | "2023-07-14T03:07:41Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,542 | ["deploy/kubernetes/dolphinscheduler/templates/statefulset-dolphinscheduler-master.yaml", "deploy/kubernetes/dolphinscheduler/templates/statefulset-dolphinscheduler-worker.yaml", "deploy/kubernetes/dolphinscheduler/templates/svc-dolphinscheduler-alert.yaml", "deploy/kubernetes/dolphinscheduler/templates/svc-dolphinscheduler-api.yaml", "deploy/kubernetes/dolphinscheduler/templates/svc-dolphinscheduler-master-headless.yaml", "deploy/kubernetes/dolphinscheduler/templates/svc-dolphinscheduler-worker-headless.yaml", "deploy/kubernetes/dolphinscheduler/values.yaml"] | [Improvement][K8S] improve the overall project observability on K8S | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Adding prometheus serviceMonitor will help improve the overall project observability
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14542 | https://github.com/apache/dolphinscheduler/pull/14539 | 027d66d200e8820e58e407b33d78c676541cf34b | f5be784044a191cd305c2979c52378f6115b3984 | "2023-07-13T10:08:26Z" | java | "2023-07-17T08:01:05Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,537 | ["dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/utils/DagHelper.java", "dolphinscheduler-service/src/test/java/org/apache/dolphinscheduler/service/utils/DagHelperTest.java"] | [Bug] [SwitchTask] f the branch that needs to be executed overlaps with another branch, it may not be able to complete the normal execution | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
For switch type tasks, if the branch that needs to be executed overlaps with another branch, it may not be able to complete the normal execution
### What you expected to happen
For switch type tasks, if the branch that needs to be executed overlaps with another branch, it may not be able to complete the normal execution
### How to reproduce
only disjoint nodes are stored in the skipNodeList collection
### Anything else
I also want to push to the 3.0.x branch
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14537 | https://github.com/apache/dolphinscheduler/pull/14563 | 2f3ab18b29ee358df3776985562a385ce0443238 | b391b74df4baf7b6f90df79df584e391ee799279 | "2023-07-13T08:51:49Z" | java | "2023-08-01T03:04:31Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,533 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/ProcessUtils.java"] | [Improvement][Worker] No need to kill remote app when appid is empty | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
No need to kill remote app when appid is empty
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14533 | https://github.com/apache/dolphinscheduler/pull/14534 | dd9c8af05155d4d3b6bf33b6ebf8f96b9f95e537 | 09afa75a3d803281fa7f39b5f054a8fcbff1ab04 | "2023-07-13T07:04:10Z" | java | "2023-07-13T07:40:58Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,531 | ["dolphinscheduler-ui/src/components/chart/modules/Bar.tsx", "dolphinscheduler-ui/src/components/chart/modules/Pie.tsx", "dolphinscheduler-ui/src/views/projects/workflow/relation/components/Graph.tsx"] | [Bug] [UI] Tooltip not show text in light theme mode | ### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The BarChart of Task State Statistics / Process State Statistics and Graph of Workflow Relation not show tooltip text in light theme mode, while switching to dark theme, everything is ok.
In light theme
and switching to dark theme
### What you expected to happen
The Graph shows tooltip with text in light theme.
### How to reproduce
In light theme mode, Go to Home Task State Statistics / Process State Statistics Chart and Project/Workflow/Workflow Relation module.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14531 | https://github.com/apache/dolphinscheduler/pull/14532 | 1ba0aecc71739c3544953c5213511a0614dfac0e | c0d776381c20b42135e8f89ba335d7975da00522 | "2023-07-13T06:51:08Z" | java | "2023-07-18T09:56:36Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,525 | [".github/workflows/e2e-k8s.yml", "deploy/kubernetes/dolphinscheduler/values.yaml"] | [Feature][E2E-Test] Set up Minikube-Kubernetes to improve e2e test | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Currently, we don't test Kubernetes deployment and Kubernetes executor.
- For the first point, sometimes we will miss some potential bugs, see https://github.com/apache/dolphinscheduler/issues/14512
- For the second point, we often get low UT coverage, see https://sonarcloud.io/component_measures?id=apache-dolphinscheduler&pullRequest=14379&metric=new_coverage&view=list
Thus, I think we should set up Minikube Kubernetes and make some improvement about these.
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14525 | https://github.com/apache/dolphinscheduler/pull/14555 | 5ccc4cc889309ea2ae949b09cc7ecbb1d941ec67 | 5a550dd628d9f0d34684fc992a2461b1b3bb910d | "2023-07-13T01:59:35Z" | java | "2023-07-26T09:18:04Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,524 | ["dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/ProcessInstanceMapper.xml"] | [Bug] [ProcessInstance] API queryProcessInstancesByTriggerCode not working | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
```text
[ERROR] 2023-07-12 20:23:13.453 +0800 org.apache.dolphinscheduler.api.exceptions.ApiExceptionHandler:[52]
org.springframework.jdbc.BadSqlGrammarException:
### Error querying database. Cause: org.h2.jdbc.JdbcSQLSyntaxErrorException: Ambiguous column name "update_time"; SQL statement:
select
b.id
, b.name, b.process_definition_version, b.process_definition_code, b.project_code, b.state, b.recovery, b.start_time, b.end_time, b.run_times,host,
command_type, b.command_param, b.task_depend_type, b.max_try_times, b.failure_strategy, b.warning_type,
warning_group_id, b.schedule_time, b.command_start_time, b.global_params, b.flag,
update_time, b.is_sub_process, b.executor_id, b.history_cmd,
process_instance_priority, b.worker_group,environment_code, b.timeout, b.tenant_code, b.var_pool,
dry_run, b.test_flag, b.next_process_instance_id, b.restart_time, b.state_history
from t_ds_trigger_relation a
join t_ds_process_instance b on a.job_id = b.id
where a.trigger_type = 0 and a.trigger_code = ? [90059-210]
```
### What you expected to happen
* `queryProcessInstancesByTriggerCode` should work properly.
### How to reproduce
* Call DS `queryProcessInstancesByTriggerCode` open api.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14524 | https://github.com/apache/dolphinscheduler/pull/14528 | 484f8419c4bd8d73fab7f4b3469dabf94269e077 | 06b6ea81cf9c6590b13fdfb373115fa14ca90f67 | "2023-07-12T12:33:22Z" | java | "2023-07-13T08:56:04Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,519 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/AbstractCommandExecutor.java"] | [Improvement] Remove the unused newDaemonSingleThreadExecutor | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Remove the unused newDaemonSingleThreadExecutor
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14519 | https://github.com/apache/dolphinscheduler/pull/14520 | 3e3e859c7f36c1fa705f4b8dcd7d11182a3ed7ee | c1cffba34951383854098ad160a36f842129e8fa | "2023-07-12T09:30:55Z" | java | "2023-07-12T13:03:41Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,517 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/DataSourceServiceImpl.java"] | [Bug] [dolphinscheduler-api] An error occurred while trying to access the Postgres database. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When I reviewed the DataSrouceServiceImpl.getDatabases() function, I found a logical error in the original code:
```java
if (dataSource.getType() == DbType.POSTGRESQL) {
rs = connection.createStatement().executeQuery(Constants.DATABASES_QUERY_PG);
}
rs = connection.createStatement().executeQuery(Constants.DATABASES_QUERY);
```
new code:
```java
if (dataSource.getType() == DbType.POSTGRESQL) {
rs = connection.createStatement().executeQuery(Constants.DATABASES_QUERY_PG);
} else {
rs = connection.createStatement().executeQuery(Constants.DATABASES_QUERY);
}
```
### What you expected to happen
successfully retrieved postgres databases
### How to reproduce
When using Postgre database to store metadata, the function DataSrouceServiceImpl.getDatabases() is called.
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14517 | https://github.com/apache/dolphinscheduler/pull/14574 | 9d10de6efa2b0fa610ae1d53646a38ad58254a45 | 1ba0aecc71739c3544953c5213511a0614dfac0e | "2023-07-12T07:58:37Z" | java | "2023-07-18T09:22:27Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,513 | [".github/workflows/api-test.yml", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/cases/ExecutorAPITest.java", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/pages/workflow/ExecutorPage.java"] | [Improvement][API Test] Add api tests for executor related apis | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
* Add api tests for executor related apis
* Part of #10411
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14513 | https://github.com/apache/dolphinscheduler/pull/14500 | 4111acb58e1ae5e5c67047f995d59d91a496f10f | 3e3e859c7f36c1fa705f4b8dcd7d11182a3ed7ee | "2023-07-12T03:34:01Z" | java | "2023-07-12T05:48:07Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,503 | ["dolphinscheduler-worker/src/main/java/org/apache/dolphinscheduler/server/worker/processor/WorkerTaskKillProcessor.java"] | [Bug] [Worker] Cannot kill the subprocess | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
worker cannot kill the subprocess
### What you expected to happen
subprocess could be killed
### How to reproduce
* create a shell task with `sleep 300`
* kill the task
* `sleep 300` is still running
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14503 | https://github.com/apache/dolphinscheduler/pull/14504 | 6af361a7d6ae604cf0df0b8e10b63b76c752ce31 | 5a6f1c88a345a752cec11b574ac39d241961b838 | "2023-07-11T06:50:10Z" | java | "2023-07-17T13:43:34Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,493 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java", "dolphinscheduler-master/src/test/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnableTest.java"] | [Bug] [Mater] Not got latest task intance by task code | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
We fixed that sometimes workers always throw message npe bug #14315. And find a new bug, check pre-task using task code from the task instance map. When pre task 1 ran more than once and failed in running 1 and success running 2. Using task code to get the instance will get the running 1 failed task, will fail the process
```
public Optional<TaskInstance> getTaskInstance(long taskCode) {
if (taskInstanceMap.isEmpty()) {
return Optional.empty();
}
for (TaskInstance taskInstance : taskInstanceMap.values()) {
if (taskInstance.getTaskCode() == taskCode) {
return Optional.of(taskInstance);
}
}
return Optional.empty();
}
```
Map is not sorted and got a random taskintance
### What you expected to happen
Running expect.
### How to reproduce
Add task code->task instance map
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14493 | https://github.com/apache/dolphinscheduler/pull/14529 | 8020c1539c6788841d36c5b3de0df38eca3b0aa3 | c812bf9d491de04c7ab2e3b58856a7c02b4a5729 | "2023-07-10T06:27:43Z" | java | "2023-07-14T06:51:39Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,488 | ["dolphinscheduler-ui/src/locales/en_US/security.ts", "dolphinscheduler-ui/src/locales/zh_CN/security.ts", "dolphinscheduler-ui/src/views/security/tenant-manage/components/use-modalData.ts"] | [Bug] Tenant with space in name fails to run the workflow | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
Running pipeline with tenant that has empty space in the name (e.g. "Tenant C") will fail the workflow run.
- Not much information is available in UI as to why the run failed.
### What you expected to happen
- workflow to execute successfully.
- error to be shown in task's log
- tenant admin to validate and prevent invalid names
### How to reproduce
1. Create a tenant with a name "Tenant C"
2. Assign tenant to current user
3. Run workflow
### Anything else
From the server logs
```
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.794 +0000 org.apache.dolphinscheduler.common.utils.OSUtils:[302] - [WorkflowInstance-6][TaskInstance-16] - create linux os user: Tenant C
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.794 +0000 org.apache.dolphinscheduler.common.utils.OSUtils:[304] - [WorkflowInstance-6][TaskInstance-16] - execute cmd: sudo useradd -g root
2023-07-09 18:05:45 Tenant C
2023-07-09 18:05:45 [ERROR] 2023-07-10 01:05:45.800 +0000 org.apache.dolphinscheduler.common.utils.OSUtils:[288] - [WorkflowInstance-6][TaskInstance-16] - Usage: useradd [options] LOGIN
2023-07-09 18:05:45 useradd -D
2023-07-09 18:05:45 useradd -D [options]
2023-07-09 18:05:45
2023-07-09 18:05:45 Options:
2023-07-09 18:05:45 -b, --base-dir BASE_DIR base directory for the home directory of the
2023-07-09 18:05:45 new account
2023-07-09 18:05:45 -c, --comment COMMENT GECOS field of the new account
2023-07-09 18:05:45 -d, --home-dir HOME_DIR home directory of the new account
2023-07-09 18:05:45 -D, --defaults print or change default useradd configuration
2023-07-09 18:05:45 -e, --expiredate EXPIRE_DATE expiration date of the new account
2023-07-09 18:05:45 -f, --inactive INACTIVE password inactivity period of the new account
2023-07-09 18:05:45 -g, --gid GROUP name or ID of the primary group of the new
2023-07-09 18:05:45 account
2023-07-09 18:05:45 -G, --groups GROUPS list of supplementary groups of the new
2023-07-09 18:05:45 account
2023-07-09 18:05:45 -h, --help display this help message and exit
2023-07-09 18:05:45 -k, --skel SKEL_DIR use this alternative skeleton directory
2023-07-09 18:05:45 -K, --key KEY=VALUE override /etc/login.defs defaults
2023-07-09 18:05:45 -l, --no-log-init do not add the user to the lastlog and
2023-07-09 18:05:45 faillog databases
2023-07-09 18:05:45 -m, --create-home create the user's home directory
2023-07-09 18:05:45 -M, --no-create-home do not create the user's home directory
2023-07-09 18:05:45 -N, --no-user-group do not create a group with the same name as
2023-07-09 18:05:45 the user
2023-07-09 18:05:45 -o, --non-unique allow to create users with duplicate
2023-07-09 18:05:45 (non-unique) UID
2023-07-09 18:05:45 -p, --password PASSWORD encrypted password of the new account
2023-07-09 18:05:45 -r, --system create a system account
2023-07-09 18:05:45 -R, --root CHROOT_DIR directory to chroot into
2023-07-09 18:05:45 -s, --shell SHELL login shell of the new account
2023-07-09 18:05:45 -u, --uid UID user ID of the new account
2023-07-09 18:05:45 -U, --user-group create a group with the same name as the user
2023-07-09 18:05:45 -Z, --selinux-user SEUSER use a specific SEUSER for the SELinux user mapping
2023-07-09 18:05:45
2023-07-09 18:05:45
2023-07-09 18:05:45 org.apache.dolphinscheduler.common.shell.AbstractShell$ExitCodeException: Usage: useradd [options] LOGIN
2023-07-09 18:05:45 useradd -D
2023-07-09 18:05:45 useradd -D [options]
2023-07-09 18:05:45
2023-07-09 18:05:45 Options:
2023-07-09 18:05:45 -b, --base-dir BASE_DIR base directory for the home directory of the
2023-07-09 18:05:45 new account
2023-07-09 18:05:45 -c, --comment COMMENT GECOS field of the new account
2023-07-09 18:05:45 -d, --home-dir HOME_DIR home directory of the new account
2023-07-09 18:05:45 -D, --defaults print or change default useradd configuration
2023-07-09 18:05:45 -e, --expiredate EXPIRE_DATE expiration date of the new account
2023-07-09 18:05:45 -f, --inactive INACTIVE password inactivity period of the new account
2023-07-09 18:05:45 -g, --gid GROUP name or ID of the primary group of the new
2023-07-09 18:05:45 account
2023-07-09 18:05:45 -G, --groups GROUPS list of supplementary groups of the new
2023-07-09 18:05:45 account
2023-07-09 18:05:45 -h, --help display this help message and exit
2023-07-09 18:05:45 -k, --skel SKEL_DIR use this alternative skeleton directory
2023-07-09 18:05:45 -K, --key KEY=VALUE override /etc/login.defs defaults
2023-07-09 18:05:45 -l, --no-log-init do not add the user to the lastlog and
2023-07-09 18:05:45 faillog databases
2023-07-09 18:05:45 -m, --create-home create the user's home directory
2023-07-09 18:05:45 -M, --no-create-home do not create the user's home directory
2023-07-09 18:05:45 -N, --no-user-group do not create a group with the same name as
2023-07-09 18:05:45 the user
2023-07-09 18:05:45 -o, --non-unique allow to create users with duplicate
2023-07-09 18:05:45 (non-unique) UID
2023-07-09 18:05:45 -p, --password PASSWORD encrypted password of the new account
2023-07-09 18:05:45 -r, --system create a system account
2023-07-09 18:05:45 -R, --root CHROOT_DIR directory to chroot into
2023-07-09 18:05:45 -s, --shell SHELL login shell of the new account
2023-07-09 18:05:45 -u, --uid UID user ID of the new account
2023-07-09 18:05:45 -U, --user-group create a group with the same name as the user
2023-07-09 18:05:45 -Z, --selinux-user SEUSER use a specific SEUSER for the SELinux user mapping
2023-07-09 18:05:45
2023-07-09 18:05:45
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.shell.AbstractShell.runCommand(AbstractShell.java:207)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.shell.AbstractShell.run(AbstractShell.java:122)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.shell.ShellExecutor.execute(ShellExecutor.java:126)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.shell.ShellExecutor.execCommand(ShellExecutor.java:103)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.shell.ShellExecutor.execCommand(ShellExecutor.java:86)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.utils.OSUtils.exeShell(OSUtils.java:412)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.utils.OSUtils.exeCmd(OSUtils.java:401)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.utils.OSUtils.createLinuxUser(OSUtils.java:305)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.utils.OSUtils.createUser(OSUtils.java:284)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.common.utils.OSUtils.createUserIfAbsent(OSUtils.java:260)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.server.worker.processor.TaskDispatchProcessor.process(TaskDispatchProcessor.java:130)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.server.worker.processor.TaskDispatchProcessor$$FastClassBySpringCGLIB$$405f5d7.invoke(<generated>)
2023-07-09 18:05:45 at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:783)
2023-07-09 18:05:45 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
2023-07-09 18:05:45 at io.micrometer.core.aop.CountedAspect.interceptAndRecord(CountedAspect.java:199)
2023-07-09 18:05:45 at sun.reflect.GeneratedMethodAccessor661.invoke(Unknown Source)
2023-07-09 18:05:45 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-07-09 18:05:45 at java.lang.reflect.Method.invoke(Method.java:498)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
2023-07-09 18:05:45 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
2023-07-09 18:05:45 at io.micrometer.core.aop.TimedAspect.processWithTimer(TimedAspect.java:192)
2023-07-09 18:05:45 at io.micrometer.core.aop.TimedAspect.timedMethod(TimedAspect.java:170)
2023-07-09 18:05:45 at sun.reflect.GeneratedMethodAccessor682.invoke(Unknown Source)
2023-07-09 18:05:45 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-07-09 18:05:45 at java.lang.reflect.Method.invoke(Method.java:498)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
2023-07-09 18:05:45 at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
2023-07-09 18:05:45 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
2023-07-09 18:05:45 at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
2023-07-09 18:05:45 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
2023-07-09 18:05:45 at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:698)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.server.worker.processor.TaskDispatchProcessor$$EnhancerBySpringCGLIB$$c1beefea.process(<generated>)
2023-07-09 18:05:45 at org.apache.dolphinscheduler.remote.handler.NettyServerHandler.lambda$processReceived$0(NettyServerHandler.java:129)
2023-07-09 18:05:45 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2023-07-09 18:05:45 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2023-07-09 18:05:45 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2023-07-09 18:05:45 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2023-07-09 18:05:45 at java.lang.Thread.run(Thread.java:750)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.800 +0000 org.apache.dolphinscheduler.common.utils.OSUtils:[261] - [WorkflowInstance-6][TaskInstance-16] - create user Tenant C fail
2023-07-09 18:05:45 [ERROR] 2023-07-10 01:05:45.801 +0000 org.apache.dolphinscheduler.server.worker.processor.TaskDispatchProcessor:[135] - [WorkflowInstance-6][TaskInstance-16] - tenantCode: Tenant C does not exist, taskInstanceId: 16
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.803 +0000 org.apache.dolphinscheduler.server.master.processor.TaskExecuteResponseProcessor:[69] - [WorkflowInstance-6][TaskInstance-16] - Received task execute result, event: TaskEvent(taskInstanceId=16, workerAddress=172.17.0.3:1234, state=FAILURE, startTime=null, endTime=Mon Jul 10 01:05:45 UTC 2023, executePath=null, logPath=/opt/dolphinscheduler/logs/20230710/10178560383904_5-6-16.log, processId=0, appIds=null, event=RESULT, varPool=[], channel=[id: 0x4949f6bb, L:/172.17.0.3:5678 - R:/172.17.0.3:47338], processInstanceId=6)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.925 +0000 org.apache.dolphinscheduler.server.master.processor.queue.TaskExecuteRunnable:[57] - [WorkflowInstance-6][TaskInstance-16] - Handle task event begin: TaskEvent(taskInstanceId=16, workerAddress=172.17.0.3:1234, state=null, startTime=null, endTime=null, executePath=null, logPath=null, processId=0, appIds=null, event=DISPATCH, varPool=null, channel=null, processInstanceId=6)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.926 +0000 org.apache.dolphinscheduler.server.master.processor.queue.TaskExecuteRunnable:[60] - [WorkflowInstance-6][TaskInstance-16] - Handle task event finished: TaskEvent(taskInstanceId=16, workerAddress=172.17.0.3:1234, state=null, startTime=null, endTime=null, executePath=null, logPath=null, processId=0, appIds=null, event=DISPATCH, varPool=null, channel=null, processInstanceId=6)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.926 +0000 org.apache.dolphinscheduler.server.master.processor.queue.TaskExecuteRunnable:[57] - [WorkflowInstance-6][TaskInstance-16] - Handle task event begin: TaskEvent(taskInstanceId=16, workerAddress=172.17.0.3:1234, state=FAILURE, startTime=null, endTime=Mon Jul 10 01:05:45 UTC 2023, executePath=null, logPath=/opt/dolphinscheduler/logs/20230710/10178560383904_5-6-16.log, processId=0, appIds=null, event=RESULT, varPool=[], channel=[id: 0x4949f6bb, L:/172.17.0.3:5678 - R:/172.17.0.3:47338], processInstanceId=6)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.927 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteThreadPool:[98] - [WorkflowInstance-6][TaskInstance-16] - Submit state event success, stateEvent: StateEvent(key=null, type=TASK_STATE_CHANGE, executionStatus=FAILURE, taskInstanceId=16, taskCode=0, processInstanceId=6, context=null, channel=null)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.927 +0000 org.apache.dolphinscheduler.server.master.processor.queue.TaskExecuteRunnable:[60] - [WorkflowInstance-6][TaskInstance-16] - Handle task event finished: TaskEvent(taskInstanceId=16, workerAddress=172.17.0.3:1234, state=FAILURE, startTime=null, endTime=Mon Jul 10 01:05:45 UTC 2023, executePath=null, logPath=/opt/dolphinscheduler/logs/20230710/10178560383904_5-6-16.log, processId=0, appIds=null, event=RESULT, varPool=[], channel=[id: 0x4949f6bb, L:/172.17.0.3:5678 - R:/172.17.0.3:47338], processInstanceId=6)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.927 +0000 org.apache.dolphinscheduler.server.master.processor.queue.TaskExecuteThreadPool:[114] - [WorkflowInstance-0][TaskInstance-0] - [WorkflowInstance-6] persist events succeeded
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.928 +0000 org.apache.dolphinscheduler.server.worker.processor.TaskExecuteResultAckProcessor:[61] - [WorkflowInstance-0][TaskInstance-0] - task execute response ack command : TaskExecuteAckCommand(super=BaseCommand(messageSenderAddress=172.17.0.3:5678, messageReceiverAddress=172.17.0.3:1234, messageSendTime=1688951145927), taskInstanceId=16, status=7)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.939 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[270] - [WorkflowInstance-6][TaskInstance-16] - Begin to handle state event, StateEvent(key=null, type=TASK_STATE_CHANGE, executionStatus=FAILURE, taskInstanceId=16, taskCode=0, processInstanceId=6, context=null, channel=null)
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.939 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[364] - [WorkflowInstance-6][TaskInstance-16] - TaskInstance finished task code:10178557080224 state:FAILURE
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.939 +0000 org.apache.dolphinscheduler.server.master.runner.StateWheelExecuteThread:[194] - [WorkflowInstance-6][TaskInstance-16] - remove task instance from timeout check list
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.939 +0000 org.apache.dolphinscheduler.server.master.runner.StateWheelExecuteThread:[217] - [WorkflowInstance-6][TaskInstance-16] - remove task instance from retry check list
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.StateWheelExecuteThread:[236] - [WorkflowInstance-6][TaskInstance-16] - Removed task instance from state check list
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1684] - [WorkflowInstance-6][TaskInstance-16] - add task to stand by list, task name:Yellow_23n, task id:0, task code:10178587069344
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1810] - [WorkflowInstance-6][TaskInstance-16] - Task dependent result is failed, taskInstanceId:0 depend result : FAILED
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1448] - [WorkflowInstance-6][TaskInstance-16] - The current process has failed task, the current process failed
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1572] - [WorkflowInstance-6][TaskInstance-16] - The workflowInstance is failed, the workflow status is FAILURE
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.940 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1616] - [WorkflowInstance-6][TaskInstance-16] - Update workflowInstance states, origin state: RUNNING_EXECUTION, target state: FAILURE
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.941 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1645] - [WorkflowInstance-6][TaskInstance-16] - Begin to update workflow instance state , state will change from RUNNING_EXECUTION to FAILURE
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.941 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[401] - [WorkflowInstance-6][TaskInstance-16] - TaskInstance finished will try to update the workflow instance state, task code:10178557080224 state:FAILURE
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.941 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1448] - [WorkflowInstance-6][TaskInstance-16] - The current process has failed task, the current process failed
2023-07-09 18:05:45 [INFO] 2023-07-10 01:05:45.941 +0000 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[1572] - [WorkflowInstance-6][TaskInstance-16] - The workflowInstance is failed, the workflow status is FAILURE
```
### Version
dolphinscheduler-standalone-server:latest
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14488 | https://github.com/apache/dolphinscheduler/pull/14492 | 3de0b5a38cd77b8c6422debe5f3f3be781065308 | cb0866ca9be3a447192ecc07829f08edefe13056 | "2023-07-10T01:20:30Z" | java | "2023-07-10T05:33:58Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,479 | [".github/workflows/api-test.yml", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/cases/SchedulerAPITest.java", "dolphinscheduler-api-test/dolphinscheduler-api-test-case/src/test/java/org/apache/dolphinscheduler/api/test/pages/workflow/SchedulerPage.java"] | [Improvement][API Test] Add api tests for important apis in scheduler page | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
* Add api test cases for important apis in scheduler page.
* part of: #10411
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14479 | https://github.com/apache/dolphinscheduler/pull/14480 | 0b69236b04f709dd241e97482a2ac515475827b1 | 7973324229826d1b9c7db81e14c89c8b5d621c28 | "2023-07-07T06:38:59Z" | java | "2023-07-07T07:34:54Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,464 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/AbstractCommandExecutor.java"] | [Improvement][Task] Remove the useless taskResultString | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Remove the useless taskResultString
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14464 | https://github.com/apache/dolphinscheduler/pull/14465 | 61ec5e33b1fa5d6eace9a969b3ebc6d90151a695 | cff53feaeb44e38584fe7856e3612dc620ce20e7 | "2023-07-06T08:36:52Z" | java | "2023-07-06T09:31:33Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,456 | ["dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases/WorkflowE2ETest.java", "dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/pages/LoginPage.java", "dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/pages/project/workflow/WorkflowDefinitionTab.java", "dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/locales/zh_CN/project.ts", "dolphinscheduler-ui/src/views/projects/workflow/definition/components/table-action.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/index.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/timing/use-table.ts", "dolphinscheduler-ui/src/views/projects/workflow/definition/use-table.ts"] | [Improvement][UI] When making the process online the system should remind user to take care of its offline timing. | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Currently the DolphinScheduler has two different states for the process and its timing. When making the process online the system can't make its timing online at the same time.But some of users might not take enough care of this point. So I suggest to provide an obvious way to remind users.
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14456 | https://github.com/apache/dolphinscheduler/pull/14460 | a1bf597d0a348f67a3e943217dcf700e484ac9f8 | 92d2b8e33fc3c0cd7f18beaff37831363a0fcbd5 | "2023-07-05T05:06:03Z" | java | "2023-07-10T00:46:39Z" |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,447 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/K8sUtils.java"] | [Bug] [K8S-Task] The judgment in ```k8sUtils#getPodLog``` is not accurate | ### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
The judgment in ```k8sUtils#getPodLog``` is not accurate because some pods may also run in the same namespace as the pods created by DS. Therefore, the naming rules for pods may not necessarily be the same as those generated by DS.
### What you expected to happen
right
### How to reproduce
filter
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
| https://github.com/apache/dolphinscheduler/issues/14447 | https://github.com/apache/dolphinscheduler/pull/14448 | 107643dba8b33fe2e14bddd5e3d666cfc82844dc | 742a2dc780b7c84d5da52d7ede348fe9a57bbe84 | "2023-07-04T07:11:56Z" | java | "2023-07-07T04:53:16Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.