issue create hangs indefinitely on repos with issues disabled / external tracker (should fail fast) #216

New issue

Open

opened 2026-07-19 14:41:32 +00:00 by stephen · 0 comments

stephen commented

2026-07-19 14:41:32 +00:00

Owner

Summary

fj issue create (and likely other issue subcommands) hangs indefinitely with no output when the target repo has its Forgejo issue tracker disabled / externally configured (e.g. rasterstate/fjord-platform, which tracks issues in Plane). The command sits at Waiting for data... (^X or interrupt to abort) and never returns; the user must interrupt.

Repro

fj issue create -R rasterstate/fjord-platform -t "test" -F somefile.md
# → hangs; no error, no timeout

rasterstate/fjord-platform has internal Forgejo issues disabled (external tracker). A normal issues-enabled repo (e.g. rasterstate/paragon) returns fine.

Expected

Fail fast with a clear message, e.g. error: issues are disabled for rasterstate/fjord-platform (external tracker configured) and a non-zero exit — do not block on a request that will never resolve.

Likely cause / fix

The create path presumably POSTs and waits without checking repository.has_issues (or without a request timeout / non-2xx handling for the external-tracker response). Options: pre-check has_issues via the repo API and short-circuit; and/or add a client request timeout so a non-answering endpoint errors instead of hanging.

Impact

Low severity but sharp UX papercut; bit us while filing the managed-forge tier fix issues (fjord-platform routes to Plane). Repo rasterstate/fj.

## Summary `fj issue create` (and likely other issue subcommands) **hangs indefinitely with no output** when the target repo has its Forgejo issue tracker disabled / externally configured (e.g. `rasterstate/fjord-platform`, which tracks issues in Plane). The command sits at `Waiting for data... (^X or interrupt to abort)` and never returns; the user must interrupt. ## Repro ``` fj issue create -R rasterstate/fjord-platform -t "test" -F somefile.md # → hangs; no error, no timeout ``` `rasterstate/fjord-platform` has internal Forgejo issues disabled (external tracker). A normal issues-enabled repo (e.g. `rasterstate/paragon`) returns fine. ## Expected Fail fast with a clear message, e.g. `error: issues are disabled for rasterstate/fjord-platform (external tracker configured)` and a non-zero exit — do not block on a request that will never resolve. ## Likely cause / fix The create path presumably POSTs and waits without checking `repository.has_issues` (or without a request timeout / non-2xx handling for the external-tracker response). Options: pre-check `has_issues` via the repo API and short-circuit; and/or add a client request timeout so a non-answering endpoint errors instead of hanging. ## Impact Low severity but sharp UX papercut; bit us while filing the managed-forge tier fix issues (fjord-platform routes to Plane). Repo rasterstate/fj.