Skip to content

fix(cron): classify no-agent failures as script errors - #63178

Closed
visualfox-ch wants to merge 1 commit into
NousResearch:mainfrom
visualfox-ch:fix/no-agent-cron-error-summary
Closed

fix(cron): classify no-agent failures as script errors#63178
visualfox-ch wants to merge 1 commit into
NousResearch:mainfrom
visualfox-ch:fix/no-agent-cron-error-summary

Conversation

@visualfox-ch

Copy link
Copy Markdown

Summary

  • classify no_agent=True cron failures before provider/API heuristics
  • keep timeout, rate-limit, and auth-like script output source-accurate
  • add regression coverage proving script-only failures never claim a provider fallback

Problem

A script-only watchdog timeout was delivered as provider timeout with Fallback chain was exhausted, even though no_agent=True skips the LLM and provider path entirely.

Verification

  • python -m pytest tests/cron/test_cron_no_agent.py -q -o addopts= — 21 passed
  • python -m ruff check cron/scheduler.py tests/cron/test_cron_no_agent.py — passed
  • git diff --check — passed

Assisted-by: Hermes:gpt-5.6-sol

@alt-glitch alt-glitch added type/bug Something isn't working comp/cron Cron scheduler and job management P2 Medium — degraded but workaround exists labels Jul 12, 2026
@visualfox-ch

Copy link
Copy Markdown
Author

Superseded by #64474, which carries the same focused no-agent cron failure classification on current main with the targeted test suite passing.

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 P2 Medium — degraded but workaround exists type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants