You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Shell scripts initially in CRLF instead of LF (causing execution issues on Linux) #73
I am currently running a node using your repository, and I noticed something unexpected regarding the shell scripts (.sh files).
At first, several scripts were formatted with CRLF line endings instead of LF. This caused execution problems on my Linux environment (e.g., ^M characters and “bad interpreter” errors). Since running a node requires a Linux-based environment, I was surprised that the scripts were not already in LF format.
After converting them to LF, everything works normally.
Steps to Reproduce
Clone the repository on Windows
Open the .sh files (they appear in CRLF)
Try executing them on a Linux environment → execution errors
Expected Behavior
Shell scripts in repositories intended for Linux execution should use LF line endings by default.
Actual Behavior
Some .sh files were in CRLF, causing errors when running the node setup or startup scripts.
I reproduced this with Git for Windows using core.autocrlf=true. The committed scripts already use LF, but checkout converts them to CRLF. PR #92 adds a .gitattributes rule to keep shell scripts LF; regression tests pass with both Linux Git and Git for Windows.
Activity
Kewe63 commentedon Sep 14, 2026
I reproduced this with Git for Windows using core.autocrlf=true. The committed scripts already use LF, but checkout converts them to CRLF. PR #92 adds a .gitattributes rule to keep shell scripts LF; regression tests pass with both Linux Git and Git for Windows.