Skip to content

fix: normalize Windows cron shell script paths - #82491

Open
zhao0112 wants to merge 1 commit into
NousResearch:mainfrom
zhao0112:fix/82443-no-agent-path-origin
Open

zhao0112 wants to merge 1 commit into
NousResearch:mainfrom
zhao0112:fix/82443-no-agent-path-origin

Conversation

@zhao0112

@zhao0112 zhao0112 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Normalize Windows bash-script execution in cron to pass forward-slash script paths.
  • Add coverage for _cron_script_argv on Windows and non-Windows paths.

Test Plan

  • python3 -m py_compile cron/scheduler.py tests/cron/test_cron_script.py
  • pytest tests/cron/test_cron_script.py -q

Closes #82443

@alt-glitch alt-glitch added type/bug Something isn't working comp/cron Cron scheduler and job management platform/windows Native Windows-specific behavior or breakage sweeper:risk-platform-windows Sweeper risk: may break or behave differently on native Windows P2 Medium — degraded but workaround exists duplicate This issue or pull request already exists labels Aug 9, 2026
@alt-glitch

Copy link
Copy Markdown
Contributor

This was generated by AI during triage.

Duplicate of #23405: both apply the same Windows Git-Bash POSIX-path conversion at the cron shell-script argv boundary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/cron Cron scheduler and job management duplicate This issue or pull request already exists P2 Medium — degraded but workaround exists platform/windows Native Windows-specific behavior or breakage sweeper:risk-platform-windows Sweeper risk: may break or behave differently on native Windows type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: cron no_agent=true scripts broken on Windows - backslash path mangling (3+ months open)

2 participants