Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Shell scripts initially in CRLF instead of LF (causing execution issues on Linux)

Open Beginner friendly
  • Is something wrong?
#73 1 comment 0 reactions 0 assignees View on GitHub

@Kewe63 is already working on this.

Since Sep 14, 2026.

  • #92 by @Kewe63 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, shell
Domain
devops

Research direction

Inspect the repository's .sh files and reproduce the reported Windows-to-Linux clone and execution path. Convert the affected scripts to LF line endings, then verify that the node setup or startup scripts execute on Linux without ^M or bad-interpreter errors.

Written by the indexing model from the issue text.

Description

Hi,

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

  1. Clone the repository on Windows

  2. Open the .sh files (they appear in CRLF)

  3. 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.

Environment

Running node on: Linux

Repo cloned initially on: Windows

Issue: CRLF line endings in shell scripts

Suggestion

Convert all .sh files in the repository to LF

Dominant language
Shell
Stars
36.4k
Forks
643
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from inkonchain/node

All issues in inkonchain/node

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.