POSIX cron scripts using wrong Python interpreter

NousResearch/hermes-agent · cluster 123440 · cron

Data as of

Nothing open on GitHub. Fix merged in #124973. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #124973. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #124973. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where cron job Python scripts on POSIX/macOS managed installs ran under the wrong interpreter, preventing imports of Hermes modules and managed dependencies. Multiple fixes and a related issue report address selecting the correct virtual environment interpreter for these scripts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #124973 Cron .py scripts import Hermes and its dependencies again on POSIX managed-store installs (#123044, #123440, salvage #123051)

    merged to main

    files: cron/scheduler_script.py, tests/cron/conftest.py, tests/cron/test_cron_script.py

3 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1 · other 1

  • #123051 fix(cron): run POSIX .py job scripts on the selected venv interpreter · merged via another change → #123440, #124973
  • #123479 fix(cron): run scripts on selected managed venv interpreter on POSIX · superseded by another PR → #123044, #123440, #123051, #124973
  • #123525 fix(cron): run external workers and scripts on the committed environment interpreter (fixes #123400, #123440) · other
Closed issues · 1
  • Closed#123440Cron .py scripts can't import Hermes modules or managed dependencies on macOS PM-managed installs (0.21.5)
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.40: 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
Merged PRs
#124973
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
27 Sep 2026

For your agent

The same facts, typed.