fix: avoid SIGPIPE in replay's --limit path at real scale
echo "$commits" | head -n "$LIMIT" can SIGPIPE the echo writer once input exceeds the pipe buffer -- head exits after its N lines while echo is still blocked writing the rest. Under set -o pipefail + set -e this aborts the whole script with a misleading exit 141. Only surfaced against the real muse 04 copy (1459 commits, ~124KB) -- test fixtures never produced enough output to hit the pipe-buffer boundary. Fixed via a here-string, which has no live pipe/writer process to receive the signal.
sha256:29d184e4ffa6c17bd76fae759cd034724721b61d8d66bf57d1df4d40f152cc81
sha
~2
symbols
sha256:ba3383d5baa8c2bdf8ecf5b950f48b23f607b1e5a29cea12ccbe7b6cb02600ba
snapshot
~2
symbols modified
0
dead code introduced
Semantic Changes
2 symbols
Older
chore: point muse-git-backup.sh's MUSE_COPY at the fresh 'muse 0…
sha256:649be9ce77a127cd847c4f798d60104dab7fe830cbc928762fafe3deadf38839
All commits
Newer
feat: split github-push into github-push-muse/github-push-musehu…
sha256:f8f0710984d598df70394ffd024f359901c0571bd9dff90e65f91f2211f9691d
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:29d184e4ffa6c17bd76fae759cd034724721b61d8d66bf57d1df4d40f152cc81 --body "your comment"
No comments yet. Be the first to start the discussion.