fj issue edit --add-assignee errors 'not found' on an existing issue #158

New issue

Closed

opened 2026-06-14 23:49:21 +00:00 by stephen · 0 comments

stephen commented

2026-06-14 23:49:21 +00:00

Owner

Bug

fj issue edit <n> --add-assignee <user> returns error: not found: <owner>/<repo> #<n> for an issue that demonstrably EXISTS (fj issue view <n> and fj issue list both show it fine).

Repro (2026-06-14, usw-dev-01)

Created rasterstate/paragon #491 via fj issue create (succeeded, returned the URL).
fj issue view 491 --repo rasterstate/paragon -> shows the issue OK.
fj issue list --repo rasterstate/paragon -> #491 listed OK.
fj issue edit 491 --repo rasterstate/paragon --add-assignee stephen -> error: not found: rasterstate/paragon #491 (retried twice, same).

Expected

The assignee is added (stephen is the repo owner / a valid assignable user).

Notes

Other edit operations not tested in this session; the failure is specifically the assignee-edit code path returning a spurious not-found.
Same box has other known fj quirks (fj#103 run-log auth, fj#147 headless auth) - may or may not be related.
Workaround used: posted an @mention comment and asked the user to self-assign in the web UI.

## Bug `fj issue edit <n> --add-assignee <user>` returns `error: not found: <owner>/<repo> #<n>` for an issue that demonstrably EXISTS (`fj issue view <n>` and `fj issue list` both show it fine). ## Repro (2026-06-14, usw-dev-01) - Created rasterstate/paragon #491 via `fj issue create` (succeeded, returned the URL). - `fj issue view 491 --repo rasterstate/paragon` -> shows the issue OK. - `fj issue list --repo rasterstate/paragon` -> #491 listed OK. - `fj issue edit 491 --repo rasterstate/paragon --add-assignee stephen` -> `error: not found: rasterstate/paragon #491` (retried twice, same). ## Expected The assignee is added (stephen is the repo owner / a valid assignable user). ## Notes - Other edit operations not tested in this session; the failure is specifically the assignee-edit code path returning a spurious not-found. - Same box has other known fj quirks (fj#103 run-log auth, fj#147 headless auth) - may or may not be related. - Workaround used: posted an @mention comment and asked the user to self-assign in the web UI.

stephen referenced this issue from a commit

2026-06-15 14:13:36 +00:00

Fix issue/PR add-assignee hitting a nonexistent endpoint (#158)

stephen referenced this issue from a pull request that will close it,

2026-06-15 14:13:46 +00:00

Fix issue/PR add-assignee hitting a nonexistent endpoint (#158) #161

stephen closed this issue

2026-06-15 14:30:19 +00:00

stephen referenced this issue from a commit

2026-06-15 14:30:19 +00:00

Fix issue/PR add-assignee hitting a nonexistent endpoint (#158) (#161)