Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/hive-forge/src
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas ccc6993703 hive-forge: exit after HIVE_FORGE_DEADLINE instead of hanging on a stalled forge
forgejo-api 0.11.1's sync client builds its own reqwest client with no
timeout and takes no caller-supplied client (sync.rs: new and
with_user_agent are the only constructors), so a forge that accepts a
connection and then stalls blocked every typed verb forever.

A watchdog thread now starts before the client is built. After
HIVE_FORGE_DEADLINE seconds (default 900, five minutes above
DOWNLOAD_TIMEOUT) it prints a hive-forge: FAILED: line and exits 75.
It bounds the whole command, not each request, and a write may already
have landed when it fires; the help text and docs/tools/forge.md say so.
2026-10-17 08:01:23 +02:00
..
verbs repo-search: don't tell the caller to raise --limit once the forge has already clamped 2026-10-14 19:37:43 +02:00
body.rs docs, prompts, hive-forge: stop handing readers the renamed verbs 2026-09-10 17:22:57 +02:00
client.rs hive-forge: exit after HIVE_FORGE_DEADLINE instead of hanging on a stalled forge 2026-10-17 08:01:23 +02:00
deadline.rs hive-forge: exit after HIVE_FORGE_DEADLINE instead of hanging on a stalled forge 2026-10-17 08:01:23 +02:00
main.rs hive-forge: exit after HIVE_FORGE_DEADLINE instead of hanging on a stalled forge 2026-10-17 08:01:23 +02:00
notify.rs check-issue-refs: catch full forge issue URLs too, drop internal links from docs entirely 2026-09-09 21:15:28 +02:00