tkrmagid/javis_bot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 20 Wiki Activity

fix: pin docker shell scripts to LF to stop CRLF breaking the image build
Some checks failed
Release / semantic-release (push) Successful in 24s
Details
tests / Unit tests (Linux, Python 3.11) (push) Failing after 5m18s
Details
Release / build-windows (push) Has been cancelled
Details
Release / build-macos (arm64, macos-latest) (push) Has been cancelled
Details
Release / build-macos (x64, macos-15-intel) (push) Has been cancelled
Details
Release / release-main (push) Has been cancelled
Details
Release / release-develop (push) Has been cancelled
Details
Release / build-linux (push) Has been cancelled
Details

Browse Source 
Windows checkouts with autocrlf=true inject CR into docker/*.sh, so inside
the Linux container `set -euxo pipefail` is read as `pipefail\r` and bash
aborts with "set: pipefail: invalid option name", failing setup-melo.sh and
the whole image build. .gitattributes already pinned .bat/.cmd/.ps1 to CRLF
but never pinned .sh, leaving all nine container scripts exposed.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
javis-bot
2026-06-22 23:27:46 +09:00
parent 00ce813845
commit 09cd4c5e31
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.gitattributes vendored
View File

@@ -7,3 +7,9 @@
# PowerShell is more forgiving but the same logic applies. # PowerShell is more forgiving but the same logic applies.
*.ps1 text eol=crlf *.ps1 text eol=crlf
# Shell scripts run inside the Linux container; they MUST stay LF even when
# checked out on Windows. autocrlf=true would otherwise inject CR and break
# `set -o pipefail`, shebangs, and heredocs (e.g. docker/setup-melo.sh failing
# the image build with "set: pipefail: invalid option name").
*.sh text eol=lf