mosaicstack/stack
16
0
Fork 1
Code Issues 335 Pull Requests 15 Actions Packages Projects Releases 15 Wiki Activity

tooling: issue-comment.sh fails on sb-it-1-dt (Configured Gitea URL not found for read-back verification) — needs REST fallback like issue-create.sh #1450

New Issue
Open
opened 2026-08-27 07:30:22 +00:00 by fred · 0 comments
fred commented 2026-08-27 07:30:22 +00:00
Collaborator
Copy Link
Copy Source

Summary

~/.config/mosaic/tools/git/issue-comment.sh fails unconditionally on host sb-it-1-dt with:

Configured Gitea URL not found for comment read-back verification

Nothing is posted (fail-closed, which is correct), but the failure means no seat on this host can attach review/CI evidence to issues or PRs through the mandatory wrapper path (Constitution gate 7). Evidence that belongs in issue threads is currently being recorded in lane TASKS.md files instead (see webui-audit lane, 2026-08-24 through 2026-08-27 entries).

Context

  • issue-create.sh on the same host succeeds via its Gitea API fallback (e.g. #1449 was filed with it), so credentials and connectivity are fine.
  • issue-comment.sh has no working API fallback for the read-back verification step: it derives the Gitea URL by a method that comes up empty here, then aborts.
  • Related but distinct: #1342 (worktreeconfig failures in pr-close.sh / issue-edit.sh on format-1 trees). This failure fires in ordinary repos too and has a different message.

Ask

Give issue-comment.sh the same REST fallback pattern issue-create.sh uses (derive host from the repo remote, token via get_gitea_token), including for the read-back verification, so comment posting works on hosts where the current URL-discovery path fails.

Repro

From any clone of a git.mosaicstack.dev repo on sb-it-1-dt:

~/.config/mosaic/tools/git/issue-comment.sh -i <n> -b "test"

Fails with the message above before posting.

## Summary `~/.config/mosaic/tools/git/issue-comment.sh` fails unconditionally on host sb-it-1-dt with: ``` Configured Gitea URL not found for comment read-back verification ``` Nothing is posted (fail-closed, which is correct), but the failure means no seat on this host can attach review/CI evidence to issues or PRs through the mandatory wrapper path (Constitution gate 7). Evidence that belongs in issue threads is currently being recorded in lane TASKS.md files instead (see webui-audit lane, 2026-08-24 through 2026-08-27 entries). ## Context - `issue-create.sh` on the same host succeeds via its Gitea API fallback (e.g. #1449 was filed with it), so credentials and connectivity are fine. - `issue-comment.sh` has no working API fallback for the read-back verification step: it derives the Gitea URL by a method that comes up empty here, then aborts. - Related but distinct: #1342 (worktreeconfig failures in pr-close.sh / issue-edit.sh on format-1 trees). This failure fires in ordinary repos too and has a different message. ## Ask Give `issue-comment.sh` the same REST fallback pattern `issue-create.sh` uses (derive host from the repo remote, token via `get_gitea_token`), including for the read-back verification, so comment posting works on hosts where the current URL-discovery path fails. ## Repro From any clone of a git.mosaicstack.dev repo on sb-it-1-dt: ``` ~/.config/mosaic/tools/git/issue-comment.sh -i <n> -b "test" ``` Fails with the message above before posting.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-infra-01 (Mosaic fleet seat code-infra-01) fargo fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) pepper rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) sanity scooby (Scooby) scrappy shaggy tiny velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1450