Skip to content
Castellan
Developer Herald's icon

Troubleshooting · Developer Herald

Read as

When the Developer Herald isn't working as it should

What to do when the Developer Herald waits for its settings, suggests nothing, misses a release, flags the wrong things, has no summaries, hits GitHub's rate limit, or its page shows only one line.

Article
1550
Applies to
Developer Herald 0.9.3
Last reviewed
For
For developers
Written for Developer Herald 0.9.3. Developer Herald is at 0.9.4 now (1 small release since: what changed).

Its page shows only one line#

"The Developer Herald is for developers": developer features are off, because it isn't hired. Hire it in Castellan, from the herald's card. While they're off, it gathers nothing.

It says "Waiting for its settings"#

It follows nothing yet. Follow a suggested feed, or add a release feed, a tracked issue, or a Hugging Face author with a search, in Settings. See Choose what the Developer Herald follows.

Nothing is suggested#

  • Reeve isn't hired: it's Reeve that finds your projects. Hire Reeve, or add release feeds yourself.
  • Your projects have no lockfile Reeve reads (npm, pnpm, yarn, Cargo, Go, a pinned requirements.txt).
  • Their packages aren't placed yet: a look asks the registries at most 200 times, and the rest wait for the next look. The page says how many aren't placed yet. Look again carries on.
  • You follow, own or dismissed them all. Dismissed ones are under Suggested feeds in Settings (Advanced), to bring back.

A release you expected isn't there#

  • It came out before you followed the feed: that's the baseline, never news. The feed's latest release still shows under Feeds.
  • More than 10 releases came out between two rounds: raise Releases read per repo.
  • The feed is quiet unless relevant, and the release matched no keyword: it's listed quietly, folded below the news.
  • It's a draft: drafts are never news.

Releases are flagged relevant, or not, unexpectedly#

Keywords match case for case, and never as the tail of a longer word. Check the quoted lines on the item: they show exactly what matched. A bare #n counts only in the tracked issue's own repository. See What's relevant.

Too much news#

Turn on Quiet unless relevant for a busy feed, add keywords so the releases that matter are flagged, and Mark all read to start clean.

There are no summaries#

The line on each item says why:

  • The local AI isn't set up: see Set up the local AI.
  • "Busy: summaries deferred to a later round": the accelerators were busy. The next round tries again.
  • Plain-words notes or Model calls per round is off in Settings.

GitHub feeds wait, or fail#

  • The rate limit: without the GitHub CLI signed in, GitHub allows 60 requests an hour. Install the GitHub CLI and sign in (gh auth login) for 5,000. The page's GitHub card says which it's using.
  • Offline: a feed shows "offline", keeps what it had, and is read again next round.
  • A feed shows an error: it's GitHub's answer, as it came. A repository that was renamed, deleted or made private can't be read: change or remove the feed in Settings.

Its page won't open#

Its page is http://developer-herald.localhost:19898/. Open on the herald's card in Castellan starts it if it's down. It starts at sign-in from the scheduled task \Developer Herald\Home page.

Still stuck?#

Write to us at support@castellan-software.com with the Developer Herald's version (on its card in Castellan), the feed, and what its page says.

Is this page right?

If something on it is wrong or out of date, tell us and we'll fix the page.

Still stuck? Write to support@castellan-software.com and mention article 1550. Every version of Developer Herald, and what changed in it, is in its release notes.