c84ef16384
A recurring job with a finite repeat count (for example repeat=3, every 24h) lost one repeat slot for each automatic re-run after a fire that could not reach the model. The failed occurrence counted, and then each 5/15/30-minute re-run of that occurrence counted again, so a half-hour outage finished a repeat=3 job with zero model calls. With cron.retry_unreachable off, the same outage costs only the one failed occurrence. Cause: cron/jobs.py:_advance_after_run bumps repeat.completed on every mark_job_run, and the re-runs parked by cron/unreachable_retry.py:plan_retry go through it like scheduled occurrences. cron/unreachable_retry.py:will_retry also treated a re-run on the last slot as the job's final run. Fix: cron/scheduler.py:_finish_completed_run passes ladder_rung=True when the dispatched instant is the parked re-run instant (new is_retry_run, which compares the dispatch snapshot's _scheduled_instant with the ladder state). mark_job_run then calls _advance_after_run with count_run=False, and will_retry leaves that run out of its final-run check the same way. The first failed occurrence still counts, and manual runs still count. (cherry picked from commit 27038f7064bb611811efee8c527dddecd4fcb57b)
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.