[Bug] start.sh script in apache-eventmesh-1.9.0/bin directory executing error in linux

[wizardzhang]

Search before asking

• [X] I had searched in the issues and found no similar issues.

Environment

Linux

EventMesh version

master

What happened

i download apache-eventmesh-1.9.0-bin.tar.gz to my cloud server, unzip the file, run the start.sh script in apache-eventmesh-1.9.0/bin directory, it show like this Because for shell files compiled under windows, each line ends with\ n\ r, while each line under linux ends with\ n

How to reproduce

download apache-eventmesh-1.9.0-bin.tar.gz to your linux server, unzip the file, run the start.sh script

Debug logs

No response

Are you willing to submit PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [ ] I agree to follow this project's Code of Conduct *

[pandaapo]

@xwm1992 Because version 1.10 is about to be released, I think it is appropriate to draw your attention to this.

[xwm1992]

you can execute the :set ff=unix to solve this problem, for version 1.10 we will take care of this problem.

[Pil0tXia]

We have resolved this problem in 1.10.0 binary dist. For developers, this problem will be addressed in https://github.com/apache/eventmesh/pull/4687.

[github-actions[bot]]

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.

[Pil0tXia]

In 1.10.0, this problem still exists. It will be fixed in the next version.

[github-actions[bot]]

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.