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
..
comments_no_paging.rs	hive-forge: comments --since --limit returns N, not at most 49	2026-10-09 21:46:14 +02:00
credential_helper.rs	hive-forge: credential-helper fails closed when the configured forge URL won't parse	2026-10-04 14:31:05 +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
pr_edit.rs	hive-forge: pr edit --base retargets a PR	2026-10-13 08:37:13 +02:00