Cron shell script resolution on Windows via Git Bash

NousResearch/hermes-agent · cluster 120504 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where cron job scripts ending in .sh or .bash on Windows incorrectly resolve to the WSL stub bash.exe rather than Git Bash, causing execution failures. The fixes replace bare which lookups with a dedicated helper to find the correct bash interpreter.

Open issues1

  • Issue#120504Cron `.sh`/`.bash` job scripts on Windows resolve to the WSL stub `bash.exe` and fail with `execvpe(/bin/bash) failed`

Open PRs2

  • PR#120509fix(cron): resolve .sh job scripts through Git Bash, not the WSL stub
  • PR#120974fix(cron): use _find_bash instead of bare which for script jobs on Windows
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.