Cairn

Windows cron scheduler bash path mangling issues

NousResearch/hermes-agent · cluster 23404 · cron

Data as of

9 open items. Fix attempted, not merged.

The short answer

3open issues
6open PRs
19items grouped
Known?
Yes. 19 related items grouped here, 4 issues already closed.
Fix event
No fix has been merged to main. 6 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 6 PRs.

These issues and PRs concern a recurring problem where cron jobs running shell scripts on Windows receive mangled backslash paths when passed to bash (Git Bash, MSYS, or WSL), causing exit 127 errors. Multiple fix attempts explore POSIX path conversion, bash resolver selection, and MSYS argv conversion as potential approaches.

Open issues3

  • Issue#23404fix(cron): bash script path mangled by backslash escaping on native Windows
  • Issue#46332[Windows] Cron jobs with .sh scripts fail because WSL bash is picked over Git Bash + backslashes get eaten by MSYS"
  • Issue#62514Windows: .sh/.bash cron jobs fail with exit 127 (backslash path collapsed by git-bash)

Open PRs6

  • PR#23405fix(cron): use POSIX paths for bash scripts on native Windows
  • PR#23489fix(cron): normalize bash script paths on Windows
  • PR#44350fix(cron): use path.as_posix() for .sh scripts on Windows
  • PR#46364fix(cron): prefer Git Bash and POSIX paths on Windows (#46332)
  • PR#99470fix(cron): fail-closed WSL bash and MSYS script argv on Windows
  • PR#103066fix(cron): prefer Git Bash over the WSL launcher for .sh cron scripts on Windows

6 PRs closed without merging

From the close comments: duplicate 2 · superseded by another PR 2 · other 2

  • #43076 fix(cron): pass shell scripts to bash with POSIX paths · other
  • #43281 fix(cron): pass shell scripts to bash with forward slashes · duplicate → #43076
  • #64257 fix(cron): pass Git Bash-friendly paths for Windows .sh jobs · superseded by another PR → #23405
  • #77393 fix(cron): pass Git-Bash-safe script path to bash on Windows (.sh exit 127 class) · superseded by another PR → #77393, #23405, #77532
  • #77532 fix(cron): resolve bash for .sh jobs via shared Windows-aware resolver (#46332) · other
Show 1 more
  • #105217 fix(cron): prefer shared Git Bash resolver for .sh jobs on Windows · duplicate → #77532
Closed issues · 4
  • Closed#43073Bug: .sh cron scripts fail on Windows - bash receives mangled backslash paths
  • Closed#60857[Bug]: Windows cron scheduler loses backslashes in script paths (C:\Users → C:Users)
  • Closed#62148bug: cron scheduler breaks Windows paths with shlex.split
  • Closed#65317fix: no_agent cron .sh scripts fail on Windows — MSYS/Git bash mangles the backslash script path (exit 127 'No such file or directory')
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.11: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Closed issues
4
Attempts
6 PRs closed without merging

For your agent

The same facts, typed.

cluster/23404.json
cluster/23404.md