status
stringclasses 1
value | repo_name
stringlengths 9
24
| repo_url
stringlengths 28
43
| issue_id
int64 1
104k
| updated_files
stringlengths 8
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 37
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
timestamp[ns, tz=UTC] | language
stringclasses 5
values | commit_datetime
timestamp[us, tz=UTC] |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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,828 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [master] Task retry reported NPE | ### 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] 2023-08-29 15:56:47.632 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[435] - [WorkflowInstance-27][TaskInstance-35] - Task finish failed, get a exception, will remove this taskInstance from completeTaskSet
java.lang.NullPointerException: id is marked non-null but is null
at org.apache.dolphinscheduler.dao.repository.BaseDao.queryById(BaseDao.java:41)
at org.apache.dolphinscheduler.dao.repository.BaseDao$$FastClassBySpringCGLIB$$ca36ec34.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:708)
at org.apache.dolphinscheduler.dao.repository.impl.TaskInstanceDaoImpl$$EnhancerBySpringCGLIB$$11409f96.queryById(<generated>)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.submitStandByTask(WorkflowExecuteRunnable.java:1902)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.retryTaskInstance(WorkflowExecuteRunnable.java:506)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.taskFinished(WorkflowExecuteRunnable.java:409)
at org.apache.dolphinscheduler.server.master.event.TaskStateEventHandler.handleStateEvent(TaskStateEventHandler.java:73)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.handleEvents(WorkflowExecuteRunnable.java:285)
### What you expected to happen
task retry success
### How to reproduce
just retry
### 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/14828 | https://github.com/apache/dolphinscheduler/pull/14829 | 6e5870d71197341a9b2a3655932de2ed24bcfb36 | 33525a17c3463d4bde56ae2335ecec38b24a5a6a | 2023-08-29T08:05:43Z | java | 2023-08-31T10:34:31Z |
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,720 | [".github/workflows/docs.yml", ".licenserc.yaml", "deploy/kubernetes/dolphinscheduler/.helmignore", "deploy/kubernetes/dolphinscheduler/README.md", "deploy/kubernetes/dolphinscheduler/README.md.gotmpl", "deploy/kubernetes/dolphinscheduler/values.yaml", "docs/docs/en/guide/installation/kubernetes.md", "docs/docs/zh/guide/installation/kubernetes.md", "pom.xml"] | [Improvement][Helm] using helm-docs to generate docs automatically | ### 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
We can use some tools like [helm-docs](github.com/norwoodj/helm-docs) to generate README automatically. Manual maintenance of [this document](https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/guide/installation/kubernetes.md#appendix-configuration) should be avoided as it can easily lead to omissions or inconsistencies.
### 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/14720 | https://github.com/apache/dolphinscheduler/pull/15299 | 93ea5f64c31311ab066d2093dbecd6e2f4215c68 | 1c1d4bd59297942499a8242066de1c8ae0143a58 | 2023-08-08T09:06:06Z | java | 2023-12-29T03:24:37Z |
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,714 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [master] NPE exception when workflow fault tolerance start | ### 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] 2023-08-07 16:32:11.287 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[737] - [WorkflowInstance-0][TaskInstance-0] - Start workflow error
java.lang.NullPointerException: null
at org.apache.dolphinscheduler.service.expand.CuringParamsServiceImpl.preBuildBusinessParams(CuringParamsServiceImpl.java:272)
at org.apache.dolphinscheduler.server.master.runner.execute.TaskExecutionContextFactory.createTaskExecutionContext(TaskExecutionContextFactory.java:124)
at org.apache.dolphinscheduler.server.master.runner.execute.DefaultTaskExecuteRunnableFactory.createTaskExecuteRunnable(DefaultTaskExecuteRunnableFactory.java:53)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.tryToTakeOverTaskInstance(WorkflowExecuteRunnable.java:1410)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.submitPostNode(WorkflowExecuteRunnable.java:1298)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.startWorkflow(WorkflowExecuteRunnable.java:731)
at org.apache.dolphinscheduler.server.master.runner.IWorkflowExecuteRunnable.call(IWorkflowExecuteRunnable.java:27)
### What you expected to happen
refer What happened
### How to reproduce
When one master node hangs and another node is fault-tolerant
### Anything else

The null pointer is because 'processInstance' is null, which comes from the cached 'taskInstance' in the 'taskInstanceMap'. So it's necessary to ensure that the 'processInstance' has been placed in the 'taskInstance' before caching. And I don't think this is a good design with other attributes in DO.
### 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/14714 | https://github.com/apache/dolphinscheduler/pull/14718 | 11d1df2f326a426b6f62aea2a45dbce5722e7b5b | 7c37a7f9feb9df0f3c92ccab4dfdb67e25d1bfae | 2023-08-07T08:47:38Z | java | 2023-08-09T05:41:28Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,698 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/MasterSchedulerBootstrap.java", "dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteContextFactory.java", "dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnableFactory.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] NPE on Master | ### 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 found some NullPointerExceptions on the master server.
```
[INFO] 2023-08-03 10:58:00.014 +0800 org.apache.dolphinscheduler.scheduler.quartz.ProcessScheduleTask:[68] - [WorkflowInstance-0][TaskInstance-0] - scheduled fire time :Thu Aug 03 10:58:00 CST 2023, fire time :Thu Aug 03 10:58:00 CST 2023, scheduleId :5
[INFO] 2023-08-03 10:58:00.406 +0800 org.apache.dolphinscheduler.server.master.runner.MasterSchedulerBootstrap:[178] - [WorkflowInstance-0][TaskInstance-0] - Master schedule bootstrap loop command success, fetch command size: 1, cost: 2ms, current slot: 0, total slot size: 1
[ERROR] 2023-08-03 10:58:00.423 +0800 org.apache.dolphinscheduler.server.master.runner.MasterSchedulerBootstrap:[147] - [WorkflowInstance-0][TaskInstance-0] - Master handle command 6601 error
org.apache.dolphinscheduler.server.master.exception.WorkflowCreateException: Create workflow execute runnable failed
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnableFactory.createWorkflowExecuteRunnable(WorkflowExecuteRunnableFactory.java:95)
at org.apache.dolphinscheduler.server.master.runner.MasterSchedulerBootstrap.lambda$run$0(MasterSchedulerBootstrap.java:136)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
at java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:159)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:173)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:650)
at org.apache.dolphinscheduler.server.master.runner.MasterSchedulerBootstrap.run(MasterSchedulerBootstrap.java:133)
Caused by: java.lang.NullPointerException: null
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteContextFactory.createWorkflowInstance(WorkflowExecuteContextFactory.java:79)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteContextFactory.createWorkflowExecuteRunnableContext(WorkflowExecuteContextFactory.java:54)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnableFactory.createWorkflowExecuteRunnable(WorkflowExecuteRunnableFactory.java:81)
... 15 common frames omitted
[INFO] 2023-08-03 10:58:31.177 +0800 org.apache.dolphinscheduler.server.master.runner.StateWheelExecuteThread:[315] - [WorkflowInstance-6581][TaskInstance-0] - [TaskInstanceKey-10444805098592:3]The task instance can retry, will retry this task instance
[INFO] 2023-08-03 10:58:31.177 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteThreadPool:[101] - [WorkflowInstance-6581][TaskInstance-0] - Submit state event success, stateEvent: TaskStateEvent(processInstanceId=6581, taskInstanceId=null, taskCode=10444805098592, status=TaskExecutionStatus{code=1, desc='running'}, type=TASK_RETRY, key=null, channel=null, context=null)
[INFO] 2023-08-03 10:58:31.259 +0800 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[290] - [WorkflowInstance-6581][TaskInstance-null] - Begin to handle state event, TaskStateEvent(processInstanceId=6581, taskInstanceId=null, taskCode=10444805098592, status=TaskExecutionStatus{code=1, desc='running'}, type=TASK_RETRY, key=null, channel=null, context=null)
```
We have currently identified that the NPE is caused by the fact that this piece of code returns null.
https://github.com/apache/dolphinscheduler/blob/5ec9085113c989c06a23d0e6820627b147dad15e/dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/process/ProcessServiceImpl.java#L331-L335
@ruanwenjun PTAL. ref: https://github.com/apache/dolphinscheduler/pull/14544
### What you expected to happen
no NPE error
### How to reproduce
A new cluster has been deployed through k8s with the dev branch, and MySQL is used as the database. The following steps were taken:
1. Created a shell task with the script content 'exit 10086;' and set the task to retry once.
2. Created a corresponding workflow with a serial wait execution policy.
3. Created a scheduled task to execute every minute.
After waiting for the task to execute several times, a NullPointerException error log appeared.
### 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/14698 | https://github.com/apache/dolphinscheduler/pull/14703 | 4bae7b1ae24e4437b844b701d2524c45ad053c97 | db62ce0e470ab8b7ae20a24c135e9e26203b897b | 2023-08-03T09:34:51Z | java | 2023-08-04T15:43:57Z |
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,686 | ["dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/AlertSendStatusMapper.xml"] | [Bug] [Alert] batchInsert execption2 | ### 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/14675 https://github.com/apache/dolphinscheduler/issues/14676
After resolving the previous issue, there is still a lingering problem.
When I configure an alarm instance for the alarm group, everything works fine. However, when I configure two alarm instances for the alarm group, there is an issue with bulk insertion.
The exception in alert-server is as follows:
```
[ERROR] 2023-08-01 19:55:05.286 +0800 org.apache.dolphinscheduler.alert.service.AlertBootstrapService:[90] - Alert sender thread meet an exception
org.springframework.jdbc.BadSqlGrammarException:
### Error updating database. Cause: java.sql.SQLException: Column count doesn't match value count at row 1
### The error may exist in class path resource [org/apache/dolphinscheduler/dao/mapper/AlertSendStatusMapper.xml]
### The error may involve defaultParameterMap
### The error occurred while setting parameters
### SQL: insert into t_ds_alert_send_status (alert_id, alert_plugin_instance_id, send_status, log, create_time) values ( ?, ?, ?, ?, ? , ?, ?, ?, ?, ? )
### Cause: java.sql.SQLException: Column count doesn't match value count at row 1
; bad SQL grammar []; nested exception is java.sql.SQLException: Column count doesn't match value count at row 1
```
https://github.com/apache/dolphinscheduler/blob/139f23040a0abc14a23872d4426196d558044c61/dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/AlertSendStatusMapper.xml#L21-L31
### 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?
- [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/14686 | https://github.com/apache/dolphinscheduler/pull/14687 | dec5228d62400dda1fd3aef2d6a12473f86fd57b | a5f5aacb5dc58dc05cd7c98c6614e44e2f4f6140 | 2023-08-02T06:25:21Z | java | 2023-08-03T10:15:09Z |
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,679 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java", "dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/UserMapper.xml"] | [Improvement][security] get-user-info API endpoint should not return the user's password in MD5 format | ### 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 get-user-info API endpoint currently returns the user's password in MD5 format, which is then stored in the local storage by the web front-end.
https://github.com/apache/dolphinscheduler/blob/37ecd262ee9a2228f0daf84e336dcfdd6f2ae9ad/dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/UsersController.java#L447-L450
https://github.com/apache/dolphinscheduler/blob/37ecd262ee9a2228f0daf84e336dcfdd6f2ae9ad/dolphinscheduler-ui/src/views/login/use-login.ts#L44-L45
However, there is no functionality that requires the use of this password. Moreover, this password is just a simple MD5 hash, which can be easily cracked.
https://github.com/apache/dolphinscheduler/blob/37ecd262ee9a2228f0daf84e336dcfdd6f2ae9ad/dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java#L211
Therefore, I believe that get-user-info API endpoint should not return the password in MD5 format.
### 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/14679 | https://github.com/apache/dolphinscheduler/pull/14680 | 25480ae9e75d900a969bd2df67c6e136089b6691 | a826ed2c1a797396ec71ddabe914fabafd77e977 | 2023-08-01T06:35:23Z | java | 2023-08-14T10:28:11Z |
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,668 | ["dolphinscheduler-tools/src/main/java/org/apache/dolphinscheduler/tools/resource/MigrateResourceService.java"] | [Bug] [dolphinscheduler-tools] The MigrateResourceService class failed to compile in the zookeeper 3.4.14 version | ### 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 **MigrateResourceService.java** failed to compile with the zookeeper 3.4.14 version. </br> </br>**Error Log**: /dolphinscheduler-tools/src/main/java/org/apache/dolphinscheduler/tools/resource/MigrateResourceService.java:[30,35] 找不到符号. </br>The reason is zk doesn't have `StringUtils.java` in zookeeper3.4.14. An incorrect jar package was imported.

### What you expected to happen
dolphinscheduler should build successful with zookeeper 3.4.14 version.
### How to reproduce
build dolphinscheduler with zk3.4.14
### 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/14668 | https://github.com/apache/dolphinscheduler/pull/14669 | 9963bfc612b30ab014f2a6b08790027fa6aed5fe | 139f23040a0abc14a23872d4426196d558044c61 | 2023-07-31T12:43:39Z | java | 2023-08-02T03:03:49Z |
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,576 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/UsersController.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java"] | [Bug] [dolphinscheduler-api] validated for duplicate username when creating or registering a user | ### 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 API calls to `createUser` and `registerUser` were not validated for duplicate username.
https://github.com/apache/dolphinscheduler/blob/c0d776381c20b42135e8f89ba335d7975da00522/dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/UsersController.java#L106-L117
https://github.com/apache/dolphinscheduler/blob/c0d776381c20b42135e8f89ba335d7975da00522/dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/UsersController.java#L565-L574
should refer to the `verifyUserName` for verification
https://github.com/apache/dolphinscheduler/blob/c0d776381c20b42135e8f89ba335d7975da00522/dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/controller/UsersController.java#L494-L496
### What you expected to happen
validated for duplicate username when creating or registering a user.
### How to reproduce
This is verified by repeatedly calling the API with the same parameters.
### 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/14576 | https://github.com/apache/dolphinscheduler/pull/14577 | 9778652f171d71266c47468be5bf478ded9cad42 | 804b7156431bb63e3d67205622cf4bf127d1d0e8 | 2023-07-18T10:16:54Z | java | 2023-07-19T04:58:00Z |
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,470 | ["README_zh_CN.md"] | [Doc] Modify some incorrect sentences and spelling errors in README_zh_CN.md documents | ### 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


### Documentation Links
https://github.com/apache/dolphinscheduler/blob/dev/README_zh_CN.md
### 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/14470 | https://github.com/apache/dolphinscheduler/pull/14471 | d6735e8eccb8c149510a7c24b10375457614e1ae | a1bf597d0a348f67a3e943217dcf700e484ac9f8 | 2023-07-06T11:24:52Z | java | 2023-07-07T10:48: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 |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,442 | ["dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/locales/zh_CN/menu.ts", "dolphinscheduler-ui/src/locales/zh_CN/project.ts", "dolphinscheduler-ui/src/router/modules/projects.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-hive-cli.ts"] | [Improvement][UI] Uniformly set the label name of 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
Uniformly set the label name of 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/14442 | https://github.com/apache/dolphinscheduler/pull/14443 | 13dfa859b59ae90b93a8ed29920c31b5aa05f30e | 9cbb2629d9260c4dad2da78e80a2dbe6519d542a | 2023-07-04T03:15:53Z | java | 2023-07-04T06:09:30Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,441 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/AlertPluginInstanceServiceImpl.java"] | [Bug] [Alarm Instance Manage] Search result list 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

In Alarm Instance Manage, input some special characters list '#、%、&' and click search, the back-end interface return empty result, that's right. But the front shows a list that contains result, it should show an empty list. Whether it's a front bug?
### What you expected to happen
Input some special characters list '#、%、&' and click search, the front will show an empty list.
### How to reproduce
In Alarm Instance Manage, input some special characters list '#、%、&' and click search.
### 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/14441 | https://github.com/apache/dolphinscheduler/pull/14444 | 9cbb2629d9260c4dad2da78e80a2dbe6519d542a | d8cf0f8b85af44818db70b5f8afa30d565905c8f | 2023-07-04T02:18:37Z | java | 2023-07-04T08:20:14Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,437 | ["dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-hive-cli.ts", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-resources.ts"] | [Improvement][UI] The resources field on the task form for the HiveCLI task shouldn't be required. | ### 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 choosing the execution type 'FROM_SCRIPT' and saving the HiveCLI task, the form can't be saved. Because the resources field need to be required. But in that case, the resources isn't supposed to be required. So I'll work out the kinks.

### 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/14437 | https://github.com/apache/dolphinscheduler/pull/14438 | 0f190ae3dadf4082f10f5df492085e6246fbe496 | babb8d9d85f24f3ee2ae06929a158acd9e093cd7 | 2023-07-03T08:55:15Z | java | 2023-07-03T12:50:42Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,413 | ["dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/log/remote/OssRemoteLogHandler.java", "dolphinscheduler-storage-plugin/dolphinscheduler-storage-oss/src/main/java/org/apache/dolphinscheduler/plugin/storage/oss/OssStorageOperator.java"] | [Improvement][OssStorageOperator] The ensureBucketSuccessfullyCreated() and checkBucketNameExists() method for Oss should not use ossClient.listBuckets() | ### 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 OssStorageOperator.java's `ensureBucketSuccessfullyCreated(String bucketName)` method and OssRemoteLogHandler.java's `checkBucketNameExists(String bucketName)` method, we should not use `ossClient.listBuckets()`.
The required permissions for `listBuckets()` are too extensive, if a OSS access key does not have other bucket's permissions, the project will fail to start normally, we can use the `doesBucketExist(bucket_name)` as a replacement.
### 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/14413 | https://github.com/apache/dolphinscheduler/pull/14414 | bcd1df19b8e0801297da135ae13a5504833e3cf5 | 6f901565776a643402c54c612088fc5260af37c5 | 2023-06-27T10:20:17Z | java | 2023-06-28T06:21:17Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,412 | [".asf.yaml"] | [Improvement][CI] CI of unmerged PRs should rerun if a new PR gets merged | ### 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
Suppose we have two PR A and B. A or B could pass CI but A and B together cause bugs and fail CI.
If the CI of A and B both had passed on 8 a.m. and A got merged on 9 a.m., in current settings, CI of B still looked good and could be merged. As a result, A and B together cause new bugs and PRs after them will fail the CI.
Therefore, we need to force the CI of unmerged PRs to rerun once a new PR gets merged.
Personally I have seen this kind of bugs happen in DS repo several times.
### 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/14412 | https://github.com/apache/dolphinscheduler/pull/14530 | c1cffba34951383854098ad160a36f842129e8fa | dd9c8af05155d4d3b6bf33b6ebf8f96b9f95e537 | 2023-06-27T06:34:20Z | java | 2023-07-13T06:30:28Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,397 | ["dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/TaskDefinitionLog.java"] | [Bug] [api] After the workflow is exported and imported again, no newly imported task definition appears on the workflow definition 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
Create a workflow "testImport":

The workflow has a task definition "testShell":

Export the workflow and import it again:

No task definition related to the imported workflow "testImport(1)_import_20230622145806508" was found in the task definition page:

### What you expected to happen
On the task definition page, you should list the newly imported workflow "testImport(1)_import_20230622145806508" and the associated task definition "testShell".
### How to reproduce
Refer to "What happened"
### 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/14397 | https://github.com/apache/dolphinscheduler/pull/14398 | 08805494405d8077ed84394410cb34f05d4cc8b6 | dec066f8ced4f15b900a8f3864112731ba9bfd75 | 2023-06-22T07:14:18Z | java | 2023-07-04T02:47:15Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,395 | ["dolphinscheduler-ui/src/views/datasource/list/detail.tsx", "dolphinscheduler-ui/src/views/projects/list/components/project-modal.tsx", "dolphinscheduler-ui/src/views/resource/udf/function/components/function-modal.tsx", "dolphinscheduler-ui/src/views/security/alarm-group-manage/components/alarm-group-modal.tsx", "dolphinscheduler-ui/src/views/security/cluster-manage/components/cluster-modal.tsx", "dolphinscheduler-ui/src/views/security/environment-manage/components/environment-modal.tsx", "dolphinscheduler-ui/src/views/security/tenant-manage/components/tenant-modal.tsx"] | [Improvement][UI] Description input box can not input blank | ### 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 want to type a description `It's a test project`, I can only type without blank like:
<img width="594" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/ef1e5508-9265-4fe1-b748-4cf17465331f">
It's user unfriendly for foreign 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/14395 | https://github.com/apache/dolphinscheduler/pull/14396 | 5250b253ebb6ba39099794bc9cd529b3db7b41df | 8a2c05f1ed8d9af88b7979dcc8de86b3d741bdfd | 2023-06-21T15:43:03Z | java | 2023-06-28T01:15:31Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,387 | ["dolphinscheduler-ui/src/locales/en_US/security.ts", "dolphinscheduler-ui/src/locales/zh_CN/security.ts", "dolphinscheduler-ui/src/views/security/user-manage/components/password-modal.tsx", "dolphinscheduler-ui/src/views/security/user-manage/components/use-password.ts", "dolphinscheduler-ui/src/views/security/user-manage/components/user-detail-modal.tsx", "dolphinscheduler-ui/src/views/security/user-manage/index.tsx", "dolphinscheduler-ui/src/views/security/user-manage/types.ts", "dolphinscheduler-ui/src/views/security/user-manage/use-columns.ts", "dolphinscheduler-ui/src/views/security/user-manage/use-table.ts"] | [Feature][Improvement] reset user password | ### Search before asking
### Description
sometime some user had forgot their password , the ask me to reset their password .
althought i have admin account ,but i found that i can not reset other user password.
maybe you can add this feature in account edit dialog
### 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/14387 | https://github.com/apache/dolphinscheduler/pull/14498 | 0246327083ab3d52f97051ac4bbabb6847ec6a10 | c3c2dda861e2472b8f282ee889e5d609d0d6b36c | 2023-06-21T02:38:47Z | java | 2023-07-11T04:01:49Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,378 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [Master] Trigger task execution in workflow instance page cause workflow instance keep running status | ### 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
Trigger execution of single task in workflow instance page, task can run, but the workflow instance will keep the `running` status.
<img width="421" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/2fa288a8-b878-4662-83df-d94cb058c347">
<img width="274" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/d7db7c2b-105f-4369-8cc1-d813e1da2113">
<img width="649" alt="image" src="https://github.com/apache/dolphinscheduler/assets/45198818/e775cb60-c363-494f-885f-46a839c5831f">
### What you expected to happen
Trigger execution successfully and workflow instance can show the right status.
### How to reproduce
Run task in workflow instance page
### 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/14378 | https://github.com/apache/dolphinscheduler/pull/14389 | 5cbe170e43d682e8a3418c636be16622df7b5a27 | 64e57410639e2b55ebf85261c205365e1466a90a | 2023-06-19T17:47:34Z | java | 2023-06-24T14:10:14Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,375 | ["docs/configs/docsdev.js"] | There is no sqoop part in the official website document | ### 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
There is no sqoop part in the official website document
### Documentation Links
https://dolphinscheduler.apache.org/zh-cn/docs/3.1.7
### 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/14375 | https://github.com/apache/dolphinscheduler/pull/14435 | f186cd5dab609ff5adbbe0d8b9088b69a273ab67 | 8f3d354c3c18fee6bd1fdea7e7a912d146d982d4 | 2023-06-19T08:24:03Z | java | 2023-07-03T12:36:45Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,371 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-hivecli/src/main/java/org/apache/dolphinscheduler/plugin/task/hivecli/HiveCliTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-hivecli/src/test/java/org/apache/dolphinscheduler/plugin/task/hivecli/HiveCliTaskTest.java"] | [Improvement][Hivecli] Add support for hivevar setting in hivecli 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
Add support for hivevar setting in hivecli
### 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/14371 | https://github.com/apache/dolphinscheduler/pull/14423 | dec066f8ced4f15b900a8f3864112731ba9bfd75 | 13dfa859b59ae90b93a8ed29920c31b5aa05f30e | 2023-06-19T03:56:19Z | java | 2023-07-04T06:02:23Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,368 | ["dolphinscheduler-registry/dolphinscheduler-registry-plugins/dolphinscheduler-registry-jdbc/README.md", "dolphinscheduler-registry/dolphinscheduler-registry-plugins/dolphinscheduler-registry-jdbc/src/main/java/org/apache/dolphinscheduler/plugin/registry/jdbc/JdbcRegistryConfiguration.java"] | [Improvement][Registry][Jdbc] Add option can use ds database directly | ### 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 now, the user needs to define database configuration for jdbc registry, but most users will save jdbc registry table in the same database as ds.
So add an option to give the user this choice.
### 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/14368 | https://github.com/apache/dolphinscheduler/pull/14369 | 64e57410639e2b55ebf85261c205365e1466a90a | a7b8e071b5265ae84c2361f36d426daf5243b63c | 2023-06-16T08:05:05Z | java | 2023-06-24T14:10:58Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,363 | ["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-switch.ts"] | [Improvement][UI] Add Default Branch Flow in switch 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
Add Default Branch Flow in switch 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/14363 | https://github.com/apache/dolphinscheduler/pull/14364 | 323129febb575a2ad9054ee3493c6b922a39a1d8 | 79b6db74fe258c63893724e32d54d0b1ceebb1bd | 2023-06-16T06:14:58Z | java | 2023-06-27T02:29:03Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,360 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [Master] State event handle error, get a unknown exception, will retry this event with IndexOutOfBoundsException | ### 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
```shell
[ERROR] 2023-06-16 11:50:22.653 org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable:[304] - [WorkflowInstance-239515][TaskInstance-null] - State event handle error, get a unknown exception, will retry this event: WorkflowStateEvent(processInstanceId=239515, taskInstanceId=null, status=WorkflowExecutionStatus{code=6, desc='failure'}, type=PROCESS_STATE_CHANGE, key=null, channel=null, context=null)
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:659)
at java.util.ArrayList.get(ArrayList.java:435)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.processComplementData(WorkflowExecuteRunnable.java:609)
at org.apache.dolphinscheduler.server.master.event.WorkflowStateEventHandler.handleStateEvent(WorkflowStateEventHandler.java:56)
at org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.handleEvents(WorkflowExecuteRunnable.java:289)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
```
version 3.1.4
`src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java` L608-L610
```java
if (scheduleDate == null) {
scheduleDate = complementListDate.get(0); // if complementListDate is null , IndexOutOfBoundsException
} else if (processInstance.getState().isFinished()) {
```
### What you expected to happen
No error message is sent, and the workflow ends normally.
### How to reproduce
complete data.
### 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/14360 | https://github.com/apache/dolphinscheduler/pull/14361 | 906353bbaf47b9a76ffa77940474d04b8bf77b26 | 5cbe170e43d682e8a3418c636be16622df7b5a27 | 2023-06-16T03:53:37Z | java | 2023-06-19T15:23:05Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,340 | ["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/HttpSenderTest.java"] | [Alert] [HTTP Plugin] Lose HTTP port | ### 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 config HTTP plugin with `GET` type and the URL contains a port like the below:
```
@Test
public void sendTest() {
Map<String, String> paramsMap = new HashMap<>();
paramsMap.put(HttpAlertConstants.NAME_URL, "https://www.baidu.com:443");
paramsMap.put(HttpAlertConstants.NAME_REQUEST_TYPE, "GET");
paramsMap.put(HttpAlertConstants.NAME_HEADER_PARAMS, "{\"Content-Type\":\"application/json\"}");
paramsMap.put(HttpAlertConstants.NAME_BODY_PARAMS, "{\"number\":\"13457654323\"}");
paramsMap.put(HttpAlertConstants.NAME_CONTENT_FIELD, "content");
HttpSender httpSender = new HttpSender(paramsMap);
AlertResult alertResult = httpSender.send("Fault tolerance warning");
Assert.assertEquals("true", alertResult.getStatus());
}
```
We will see the URL built info losed port:

### What you expected to happen

We need to use authority to replace the host to build URI
### How to reproduce
`URI uri = new URI(unencodeUrl.getProtocol(), unencodeUrl.getHost(), unencodeUrl.getPath(), unencodeUrl.getQuery(), null);
`
Change to:
`URI uri = new URI(unencodeUrl.getProtocol(), unencodeUrl.getAuthority(), unencodeUrl.getPath(), unencodeUrl.getQuery(), null);
`
And test again:

Works well
### 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/14340 | https://github.com/apache/dolphinscheduler/pull/14341 | b49b91c45d1c9e1ed1906b49d1fef63d753ca1ac | c1a67905149a1d791ec23dca477bc59c08c4f607 | 2023-06-13T06:38:06Z | java | 2023-06-14T09:38:58Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,334 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java"] | [Bug] [master] The complement function does not generate the next running instances in parallel 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
Use the parallel mode of the complement function, after generating an instance and successfully completing it, the next running instance will not be generated.
### What you expected to happen
Use the parallel mode of the complement function, spawn all running instances normally.
### How to reproduce
Create a new workflow definition, select the complement function, parallel mode, parallel degree 2, time range 6 days, click execute, and only 2 workflow instances will be generated as a result.
### Anything else
_No response_
### Version
3.2.0-prepare
### 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/14334 | https://github.com/apache/dolphinscheduler/pull/14335 | 1c935d901e09eab6c76375c170745c7e6ce6af14 | 75f4fa288176c5466db69381bd5b62413b31e945 | 2023-06-12T09:39:33Z | java | 2023-06-12T11:40:26Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,329 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/parser/BusinessTimeUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/test/java/org/apache/dolphinscheduler/plugin/task/api/parser/TimePlaceholderUtilsTest.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-dataquality/src/main/java/org/apache/dolphinscheduler/plugin/task/dq/rule/RuleManager.java"] | [Improvement][common] Remove duplicate BusinessTimeUtils | ### 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 duplicate BusinessTimeUtils
### 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/14329 | https://github.com/apache/dolphinscheduler/pull/14330 | 75f4fa288176c5466db69381bd5b62413b31e945 | 1cd5070b5dcfdc202a3db08c426dc35053626cab | 2023-06-12T07:33:12Z | java | 2023-06-13T00:30:34Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,318 | ["dolphinscheduler-ui/package.json", "dolphinscheduler-ui/pnpm-lock.yaml", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/index.module.scss", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/index.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/use-d3-tree/index.scss", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/use-d3-tree/index.tsx", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/use-d3-tree/tree.ts", "dolphinscheduler-ui/src/views/projects/workflow/definition/tree/use-d3-tree/util.ts"] | [Improvement][UI] migrate version 2.x workflow definition d3 tree view to version 3.x | ### 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
1. When rendering the tree view component using echarts on workflow-definition page in version 3.x , I noticed that the task state of the tree nodes is only based on the first instance, which may not be accurate.
2. The echarts tree conceals other instance information in version 3.x . I think the approach used in version 2.x, is more intuitive.
3. I want to migrate version 2.x d3 tree view and replace version 3.x.
version 2.x:
<img width="849" alt="截屏2023-04-18 14 31 43" src="https://github.com/apache/dolphinscheduler/assets/45848815/23e82dc0-dc7b-48ba-be67-f24c32e1c0f9">
version 3.x:
<img width="993" alt="截屏2023-06-09 10 11 13" src="https://github.com/apache/dolphinscheduler/assets/45848815/9f964bb8-e0b2-48bf-9c78-1e6594447903">
### 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/14318 | https://github.com/apache/dolphinscheduler/pull/14382 | babb8d9d85f24f3ee2ae06929a158acd9e093cd7 | 08805494405d8077ed84394410cb34f05d4cc8b6 | 2023-06-09T02:13:16Z | java | 2023-07-04T02:33:27Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,314 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/event/TaskStateEventHandler.java", "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] [Master] Workflow keep running when task has no id | ### 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 readyToSubmitTaskQueue contains task without id, will always running
### What you expected to happen
Stop running task
### How to reproduce
Change completeTaskMap to completeTaskSet
### Anything else
Same as #11930
### 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/14314 | https://github.com/apache/dolphinscheduler/pull/14315 | d4921fa2dda541d0fa3a198dd3052b61a73f2d37 | 465e7ae6ee44d50f6f319ddfaab82bdf77fec0e5 | 2023-06-08T09:38:26Z | java | 2023-06-14T04:53:16Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,311 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/ProcessDefinitionServiceImpl.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/TaskDefinitionServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/ProcessDefinitionServiceTest.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/TaskDefinitionServiceImplTest.java"] | [Improvement][Permission] Remove duplicate checkProjectAndAuth | ### 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 duplicate checkProjectAndAuth
### 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/14311 | https://github.com/apache/dolphinscheduler/pull/14313 | 221df4a278d1287073a6df8f164f0c5aae2de64f | 5250b253ebb6ba39099794bc9cd529b3db7b41df | 2023-06-08T07:36:27Z | java | 2023-06-27T06:01:37Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,299 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/SchedulerServiceImpl.java"] | [Bug] [schedule] The interface method creates a scheduled task without data verification | ### 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 version 3.1.7, Multiple timed tasks can be created for the same workflow through the interface. At this time, an error will be reported when querying the workflow list of the project
### What you expected to happen
It is not possible to create a second timed task for the same workflow on the page, so the interface should also limit when the workflow already has a timed task, prompting that the timed task already exists
### How to reproduce
It is not possible to create a second timed task for the same workflow on the page, so the interface should also limit when the workflow already has a timed task, prompting that the timed task already exists
### 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/14299 | https://github.com/apache/dolphinscheduler/pull/14430 | 09afa75a3d803281fa7f39b5f054a8fcbff1ab04 | 484f8419c4bd8d73fab7f4b3469dabf94269e077 | 2023-06-07T07:49:00Z | java | 2023-07-13T08:21:07Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,295 | ["dolphinscheduler-common/src/main/java/org/apache/dolphinscheduler/common/utils/FileUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/ShellCommandExecutor.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/utils/FileUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-remoteshell/src/main/java/org/apache/dolphinscheduler/plugin/task/remoteshell/RemoteShellTask.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-shell/src/main/java/org/apache/dolphinscheduler/plugin/task/shell/ShellTask.java"] | [Improvement][common] Remove the duplicate FileUtils | ### 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 duplicate FileUtils
### 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/14295 | https://github.com/apache/dolphinscheduler/pull/14301 | e7cdc7c1367b67f216bb04b8a2aab0945b75126a | 66e09dc66ec3439b53edf9fd9142506b615bae35 | 2023-06-07T05:38:08Z | java | 2023-06-08T00:59:53Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,289 | ["dolphinscheduler-ui/src/views/projects/workflow/definition/components/timing-modal.tsx"] | [Improvement][dolphinscheduler-ui] The next five execution time labels are dynamically displayed | ### 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
If I don't click the button of the execution time, the label of the next five execution times should not be displayed.

### 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/14289 | https://github.com/apache/dolphinscheduler/pull/14290 | 929811760a3cd3ae43c2f48d13275a61e0fa41f9 | 6b1a952c6b744bf9e115cb39266dee2f235a2f3c | 2023-06-07T00:51:39Z | java | 2023-06-07T06:57:48Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,286 | ["dolphinscheduler-bom/pom.xml", "dolphinscheduler-dist/release-docs/LICENSE", "dolphinscheduler-dist/release-docs/licenses/LICENSE-clickhouse-jdbc.txt", "tools/dependencies/known-dependencies.txt"] | [Improvement][BOM] Bump clickhouse-jdbc from 0.3.2-patch11 to 0.4.6 | ### 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
Bump clickhouse-jdbc from 0.3.2-patch11 to 0.4.6
* related: #14096
### 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/14286 | https://github.com/apache/dolphinscheduler/pull/14287 | 4d798e774e99f37bca2b7bcba7be54c7a8e01b98 | ed8ae9c0ee5cc214631120e6d2cf4bcf7a84b699 | 2023-06-06T08:29:23Z | java | 2023-06-07T04:08:23Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,284 | ["dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/AccessToken.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/AlertGroup.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/DataSource.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/ProcessInstanceMap.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/Queue.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/Resource.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/Tenant.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/entity/UdfFunc.java"] | [Bug] [DAO] update the check of Integer in equals() | ### 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 cannot use `!=` to compare two Integers in the `equals()` of entity
### What you expected to happen
use `Objects.equals()`
### How to reproduce
2 entities with id > 127
### Anything else
* related: #14123
### 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/14284 | https://github.com/apache/dolphinscheduler/pull/14285 | ed8ae9c0ee5cc214631120e6d2cf4bcf7a84b699 | 929811760a3cd3ae43c2f48d13275a61e0fa41f9 | 2023-06-06T07:39:27Z | java | 2023-06-07T04:08:48Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,282 | ["dolphinscheduler-ui/src/locales/en_US/project.ts", "dolphinscheduler-ui/src/locales/zh_CN/project.ts", "dolphinscheduler-ui/src/views/projects/task/instance/types.ts", "dolphinscheduler-ui/src/views/projects/task/instance/use-table.ts"] | [Improvement][Task] Add app_link on the ui of 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 feature requirement.
### Description
Add app_link on the ui of task instance
### 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/14282 | https://github.com/apache/dolphinscheduler/pull/14283 | 2c057d6a8f010b260534bdcd42f7832cab819462 | 525e441223c4355f7db993935cfe13ff548bd165 | 2023-06-06T03:38:27Z | java | 2023-06-07T07:00:12Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,280 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/enums/TaskExecutionStatus.java"] | [Improvement][Task] update the task execution status check | ### 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 the task execution status check
### 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/14280 | https://github.com/apache/dolphinscheduler/pull/14281 | d587b5f03dd5a610b81b5acda746dfef7f40102a | 4d798e774e99f37bca2b7bcba7be54c7a8e01b98 | 2023-06-06T02:44:26Z | java | 2023-06-06T07:25:57Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,269 | ["docs/docs/en/guide/resource/task-group.md", "docs/docs/zh/guide/resource/task-group.md", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/TaskGroupServiceImpl.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/controller/TaskGroupControllerTest.java", "dolphinscheduler-api/src/test/java/org/apache/dolphinscheduler/api/service/TaskGroupServiceTest.java", "dolphinscheduler-dao/src/main/java/org/apache/dolphinscheduler/dao/mapper/TaskGroupMapper.java", "dolphinscheduler-dao/src/main/resources/org/apache/dolphinscheduler/dao/mapper/TaskGroupMapper.xml", "dolphinscheduler-dao/src/test/java/org/apache/dolphinscheduler/dao/mapper/TaskGroupMapperTest.java", "dolphinscheduler-ui/src/views/resource/task-group/option/components/form-modal.tsx", "dolphinscheduler-ui/src/views/resource/task-group/option/use-table.ts"] | [Bug] [Task Group] no matter whether user is admin or non-admin, they can only use the task group created by themselves | ### 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 group is at user level so that cannot be shared among multiple users.
~~An non-admin user cannot select the task group created by others/admin when creating a task~~
~~In another word, non-admin user can only see the task group created by himself, which makes the task group an useless function.~~
### What you expected to happen
~~After a task group being created, the admin should have the option to authorize this task group to an ordinary user in User Manage page. (Now there are only file resource and udf resource can be authorized)~~
Task group should be project level or an option should be given so that this group can be shared among users.
### How to reproduce
1. Login as User A and create a project and a task group related to this project.
2. Authorize the project to user B.
3. Login in as user B and create a Task. Click "Task group name" and the drop-down box shows nothing.
### Anything else
There is no option to allow normal users to access this resource in Security management page or Resources.
### 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/14269 | https://github.com/apache/dolphinscheduler/pull/14392 | ca760aabd44e9168281fea3a9df1bab1c10b5cc7 | 759756ae80a449c1989181c70696ba59fa125922 | 2023-06-02T09:20:18Z | java | 2023-07-23T04:11:37Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,250 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-seatunnel/src/main/java/org/apache/dolphinscheduler/plugin/task/seatunnel/flink/SeatunnelFlinkParameters.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-seatunnel/src/main/java/org/apache/dolphinscheduler/plugin/task/seatunnel/flink/SeatunnelFlinkTask.java", "dolphinscheduler-ui/src/views/projects/task/components/node/fields/use-sea-tunnel.ts"] | [Bug] [Seatunnel] Run Mode defaults to run, and you cannot select a null value | ### 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 Dolphinscheduler creates a seattunnel task, if the Flink startup script is used, the Run Mode defaults to run, and a null value cannot be selected. As a result of this operation, when seatunnel invokes the Flink service to perform tasks, --run-mode run will be spliced by default in the execution command, but the run-mode parameter is not supported in multiple flink versions (tested 1.13 1.14 1.15 1.16 1.17), and finally Task execution failed.

### What you expected to happen
It is expected that a none option can be added, and the backend logic judges whether to splice the default parameters based on this field.

### How to reproduce
Create a seatunnel task and select the flink engine RunMode as run by default. When executing the task, the --run-mode run parameter will be spliced, but the run-mode parameter is not supported in multiple flink versions (tested 1.13 1.14 1.15 1.16 1.17), and the final task Execution failed.


### 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/14250 | https://github.com/apache/dolphinscheduler/pull/14267 | 175d976cd2c5d364dab70e03986c25344927f300 | 4111acb58e1ae5e5c67047f995d59d91a496f10f | 2023-06-01T02:52:31Z | java | 2023-07-12T01:06:19Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,243 | ["docs/docs/en/guide/metrics/metrics.md", "docs/docs/zh/guide/metrics/metrics.md", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/aspect/AccessLogAspect.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/metrics/ApiServerMetrics.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/MetricsCleanUpService.java", "dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/MetricsCleanUpServiceImpl.java", "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"] | [Improvement][Metrics] Add user tag of response time of api server | ### 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 user tag of response time of api server
### 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/14243 | https://github.com/apache/dolphinscheduler/pull/14248 | 5e9f1de075334f58145c585b3a02456e9342c114 | 8aec3846b4b2b186ef1e14d19493352e135549f2 | 2023-05-31T08:03:20Z | java | 2023-06-01T07:13:28Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,236 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-flink/src/main/java/org/apache/dolphinscheduler/plugin/task/flink/FlinkArgsUtils.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-flink/src/main/java/org/apache/dolphinscheduler/plugin/task/flink/FlinkConstants.java"] | [Bug] [Flink] Yarn queue conf doesn't work in flink command line. | ### 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 Yarn CommandLine always commits tasks to the default queue, even if the tenant YARN queue is specified.
### What you expected to happen
Task should be committed to the tenant YARN queue.
### How to reproduce
Run a non-sql Flink job >=1.12 with specific tenant YARN queue.
### 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/14236 | https://github.com/apache/dolphinscheduler/pull/14237 | aa2d9a7f05354c1041a6ac1e139088bf4f78b35b | de2cc0e2352c2a99ab46a036af2aab1fe24d9941 | 2023-05-29T15:05:22Z | java | 2023-06-12T03:04:39Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,219 | ["dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/ProcessDefinitionServiceImpl.java"] | [Bug] [API] TreeView "Task Status" not show bug | ### 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
TreeView "Task Status" not show
### What you expected to happen
TreeView "Task Status" show
### How to reproduce
open Workflow definition list TreeView button
### 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/14219 | https://github.com/apache/dolphinscheduler/pull/14207 | 9e0991145e5de196f30f2c7c080a6ad48fdf2bb4 | b8748e29ae27c48b6bd37ccc0bd198384c586ba1 | 2023-05-26T04:52:06Z | java | 2023-05-29T05:39:38Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,216 | ["dolphinscheduler-master/src/main/java/org/apache/dolphinscheduler/server/master/runner/WorkflowExecuteRunnable.java", "dolphinscheduler-task-plugin/dolphinscheduler-task-api/src/main/java/org/apache/dolphinscheduler/plugin/task/api/enums/TaskExecutionStatus.java"] | [Bug] [Master] workflow state keep READY_STOP when sub_process state 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
I hive fix a bug with the issue https://github.com/apache/dolphinscheduler/pull/14016
when I stopped a workflow with sub_process . sub_process state turn to STOP but workflow still READY_STOP and not change any more.
according to Master logs it seems not stop workflow suceess.
master logs :
[INFO] 2023-05-24 08:42:43.857 +0800 - set work flow 47 task 60 running
[INFO] 2023-05-24 08:42:43.873 +0800 - set sub work flow 47 task 60 state: TaskExecutionStatus{code=1, desc='running'}
[INFO] 2023-05-24 08:42:43.877 +0800 - work flow 47 task 60, sub work flow: 48 state: WorkflowExecutionStatus{code=1, desc='running'}
[INFO] 2023-05-24 08:42:48.868 +0800 - set work flow 47 task 60 running
[INFO] 2023-05-24 08:42:48.873 +0800 - work flow 47 task 60, sub work flow: 48 state: WorkflowExecutionStatus{code=1, desc='running'}
[INFO] 2023-05-24 08:42:53.877 +0800 - set work flow 47 task 60 running
[INFO] 2023-05-24 08:42:53.881 +0800 - work flow 47 task 60, sub work flow: 48 state: WorkflowExecutionStatus{code=1, desc='running'}
### What you expected to happen
workflow's state change to be STOP when sub_process's state STOP
### How to reproduce
1.create a workflow named sub_workflow with a simple shell task 'echo helloWorld sleep 60 echo helloWorld' to make the process worked longer;
2.create a workflow named main_workflow and add the sub_process 'sub_workflow ';
3.start the workflow 'main_workflow ' and after task_instance turn to running ,stop workflow;
4.you will see the 'sub_workflow ' STOP but 'main_workflow ' holding READY_STOP and master log show that process_instance 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/14216 | https://github.com/apache/dolphinscheduler/pull/14221 | fdb8fde776b5cf0719c2d0feb7f112cc3f30ddda | d587b5f03dd5a610b81b5acda746dfef7f40102a | 2023-05-26T02:49:06Z | java | 2023-06-06T03:04:32Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,201 | ["dolphinscheduler-ui/src/views/projects/workflow/instance/components/process-instance-condition.tsx", "dolphinscheduler-ui/src/views/projects/workflow/relation/index.tsx", "dolphinscheduler-ui/src/views/projects/workflow/timing/components/timing-condition.tsx"] | [Improvement][UI] Improve the select component to support users to filter options. | ### 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/14201 | https://github.com/apache/dolphinscheduler/pull/14202 | af7da0630eb1cb777da6ea1ef5508a3b237b84fb | c6ac356134504130af598a8d1d9620b67f6d3d1c | 2023-05-25T02:46:57Z | java | 2023-05-25T05:12:04Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,180 | ["dolphinscheduler-task-plugin/dolphinscheduler-task-datax/src/main/java/org/apache/dolphinscheduler/plugin/task/datax/DataxUtils.java"] | [Bug] [Datax] `getReaderPluginName` may return null | ### 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
Because of the datasouce `databend` now does not support datax reader mode so the code here will return `null` when user select `databend` as datax reader:
```java
public static String getReaderPluginName(DbType dbType) {
switch (dbType) {
case MYSQL:
return DATAX_READER_PLUGIN_MYSQL;
case POSTGRESQL:
return DATAX_READER_PLUGIN_POSTGRESQL;
case ORACLE:
return DATAX_READER_PLUGIN_ORACLE;
case SQLSERVER:
return DATAX_READER_PLUGIN_SQLSERVER;
case CLICKHOUSE:
return DATAX_READER_PLUGIN_CLICKHOUSE;
case HIVE:
return DATAX_READER_PLUGIN_RDBMS;
case PRESTO:
return DATAX_READER_PLUGIN_RDBMS;
default:
return null;
}
}
```
IMO, datax component of DS should separate the enumeration of the datasource and datatarget. And now it is enum together here:
```
type IDataBase =
| 'MYSQL'
| 'POSTGRESQL'
| 'HIVE'
| 'SPARK'
| 'CLICKHOUSE'
| 'ORACLE'
| 'SQLSERVER'
| 'DB2'
| 'PRESTO'
| 'REDSHIFT'
| 'ATHENA'
| 'TRINO'
| 'AZURESQL'
| 'STARROCKS'
| 'DAMENG'
| 'OCEANBASE'
| 'SSH'
| 'DATABEND'
| 'SNOWFLAKE'
```
### What you expected to happen
The datax reader show available reader plugin instead of return `null`
### How to reproduce
In DS UI using datax reader.
### 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/14180 | https://github.com/apache/dolphinscheduler/pull/14204 | a7b8e071b5265ae84c2361f36d426daf5243b63c | 9c92b4b240a30e54464509b2e696e3310894507a | 2023-05-23T04:10:07Z | java | 2023-06-25T08:18:38Z |
closed | apache/dolphinscheduler | https://github.com/apache/dolphinscheduler | 14,179 | ["dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-api/src/main/java/org/apache/dolphinscheduler/plugin/datasource/api/client/CommonDataSourceClient.java", "dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-azure-sql/src/main/java/org/apache/dolphinscheduler/plugin/datasource/azuresql/AzureSQLDataSourceClient.java", "dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-hive/src/main/java/org/apache/dolphinscheduler/plugin/datasource/hive/HiveDataSourceClient.java", "dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-kyuubi/src/main/java/org/apache/dolphinscheduler/plugin/datasource/kyuubi/KyuubiDataSourceClient.java", "dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-kyuubi/src/test/java/org/apache/dolphinscheduler/plugin/datasource/kyuubi/KyuubiDataSourceClientTest.java", "dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-redshift/src/main/java/org/apache/dolphinscheduler/plugin/datasource/redshift/RedshiftDataSourceClient.java"] | Driver does not support get/set network timeout for connections. (Method 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 issues.
### What happened
I I updated Dolphin 3.1.6 and tested the Hive data source connection and found 5 more long links in the HiveServer2 service that did not close。
Dolphin:

hiveservice2:

api-log:

### What you expected to happen
I expected hive datasource wiil be close
### How to reproduce
you just test hive datasource
### 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/14179 | https://github.com/apache/dolphinscheduler/pull/14193 | d92e2b360e0117259c58ea540b8b3cc2664694d8 | e4fb5b30a45b5e2380841e8b37dff2f0408fc5a7 | 2023-05-23T01:32:48Z | java | 2023-07-21T08:14:21Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.