[easy to fix list] good for new contributors

[casionone]

The following list is the latest newbie tasks (keep up to date). If you are participating in an open source project for the first time, it is recommended to choose one of the following tasks to practice. The first task is used to familiarize yourself with the submission process and feel the friendliness of the community. If you are interested in a task, Please leave a message, for example, I am interested in implementing this task, please submit a PR in 2 weeks if you leave the message. If more than 2 weeks, other contributors are welcome to do it.

😊 The current development branch is master please submit pr to this branch

For the claim of the issue task:

At present, github cannot directly assign issues to those who do not have permission to write the project repository. Only allow issues to be assigned to people who have commented on the issue. https://github.blog/2019-06-25-assign-issues-to-issue-commenters/

😊 For students who want to claim the linkis issue task and do not have warehouse write permission, they can comment under the corresponding issue. Then the administrator can assign it to you

Before submitting a PR, please read the [How to Contribute Guide to the Official Website](https://linkis.apache.org/community/how-to-contribute

---

以下是新手任务列表（持续更新中）。如果您是第一次参加开源项目，建议您选择以下任务之一进行练习。第一项任务是熟悉提交过程，感受社区的友好。如果您对某项任务感兴趣，请留言，例如，我对执行此任务感兴趣，如果您留言，请在2周内提交PR。如果超过2周，欢迎其他贡献者参与。如果有任何问题可以在下方留言，解决issue过程中的任何开发或者其他问题，社区同学会协助解决。

😊 当前开发分支为master，请提交pr至此分支

对于issue任务的认领:

目前github对于没有项目仓库写权限的人员，没法直接分配issue。只允许将issue分配给在该issue下评论过的人。 https://github.blog/2019-06-25-assign-issues-to-issue-commenters/

😊 对于想认领linkis的issue任务，又没有仓库写权限的同学，可以在【对应的issue下】评论（如:I want to fix this issues，you can assign it to me）， 然后管理员就可以分配指定给你

提交 PR 前请阅读如何参与项目贡献指南

【官网贡献指引视频 】https://www.bilibili.com/video/BV1qr4y1s7pv?share_source=copy_web
【社区贡献入门指引 PPT】 https://github.com/apache/incubator-linkis-website/blob/dev/resource/Apache%20Linkis%20(Incubating)%20Community%20Contribution%20Getting%20Started%20Guide.pdf

---

good first issue

Here are some beginner tasks for developers contributing code for the first time.

这里有一些针对初学者第一次贡献代码的任务。

• [linkis-website] [WIP][Feature][linkis-website] Looking for bugs on the linkis website #4525

---

TODO list

Here are some easy-to-fix issues or feature:

• code style issues collect #1475
• [BUG]DefaultGatewayRouter init NPE #1235
• [Web] [Bug] The deletion of configuration data is not confirmed, and there is a possibility of accidental deletion #1273
• [Web] [Bug] Some fields are missing in English internationalization #1274
• [Web] [Bug] Front-end code style check has warning:Unexpected console statement #1275
• [Web] [Bug] Some components of npm that the linkis console depends on have security vulnerabilities #1276
• [Web] [Bug] The percentage of resource usage is displayed abnormally #1277
• [module] Linkis-Gateway can not work with DELETE request without request body #1015
• [Manager] [linkis-manager-persistence ] Change SQL annotation to XML for LinkisManager Persistence module #920
• [Manager] [Bug] API /linkisManager/rm/applicationlist has NPE bug #1763
• [Bug][1.1.2] A NullPointerException could be thrown in class QueryPersistenceManager #1873
• [Feature][1.1.2] change main method test to junit5 test in module linkis-cs-cache #1890
• [Feature][1.1.2] change main method test to junit5 test in module linkis-cs-highavailable #1891
• [Feature][1.1.2] change main method test to junit5 test in module linkis-cs-listener #1892
• [Bug] remove use of sun.misc.BASE64Decoder #1411
• [Bug] upgrade hive-exec and hive-jdbc dependencies due to CVEs #1364
• [Feature] Provide an interface API to get the executor #1453
• [Bug] upgrade to hive-exec 2.3.4 due to CVE  #2184
• [Bug] [Flink] Not support YarnPerJobClusterDescriptorAdapter for FlinkSQLComputationExecutor #2393

Add Test Code Task

• [Junit5 Test] Junit5 test task url integration #2985

Scala code format alarm clear task list

• Scala code format alarm clear task url integration #2881

Error code task list

• Error code optimization and documentation checklist #3363

Documentation

• [DOC] The Linkis debug doc needs to be improved #2054
• [DOC] The Linkis cluster_deployment doc needs to be improved  #2055
• [DOC] Linkis architecture docs are not standardized and unified, some even missing #2056

In addition to the above tasks, you can also add some Unit Tests to Improve code test coverage

If you are interested in any of the above issues, please reply :”I want to fix issues [xxxxx]” in the github comment area below.

Please read the Contribution Guideline before submitting the PR

[casionone]

I want to fix issues #1144 [Bug] The engine will not automatically exit when it is in the starting state

[legendtkl]

I have submit some PRs

• Fix NPE in CsJobListener#onJobCompleted #1166 for [Bug]NPE in CsJobListener #1160
• Add JAVA_HOME for ProcessEngineConnLaunch #1167 for [Bug] Add JAVA_HOME for ProcessEngineConnLaunch #1159
• fix NPE for /linkisManager/rm/engines api #1168 for [Bug] NPE of api '/linkisManager/rm/engines' #1158

@casionone would you help review these tiny prs.

Thanks, kelu.

[legendtkl]

I have submitted some PRs

• Append shell stdout to persistent log #1172 for [Bug]Shell engine will not append shell-stdout into persisted-log #1157
• check the task code and make sure it's not empty #1173 for [Bug]Cannot be processed when the submitted task script is empty code #1143
• Add health check for node filter #1174 for [Feature]Task submit with ECM health check #1142

[Tandoy]

I will try to fix it
#1278 [Bug] Some log display formats need to be optimized

[jianwei2]

#1358 I fixed it in my company. PR will be submitted later.

[legendtkl]

Hi, we think the code styles issues would be helpful for the beginner to be familiar with the PR workflow. If you find some content satisfying the following rules, welcome to submit PRs.

Code styles can be improved:

• typo in classes/methods/fields/comments
• redundant code, such as commented code, unused class/methods/fields
• duplicated code snippet, extract the duplicated code for reusing
• refactor, maybe some best practice