mathias/hyperguild
1
0
Fork 0
Code Issues 30 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

CD broken since gitea.d-ma.be→git.d-ma.be rename: ingestion build fails go mod download on mcp-chassis module path #74

New Issue
Closed
opened 2026-06-30 19:18:03 +00:00 by mathias · 3 comments
mathias commented 2026-06-30 19:18:03 +00:00
Owner
Copy Link
Copy Source

Symptom

cd.yml (Build and deploy) has failed on every commit since ~2026-06-26 (runs 288, 290, 292…). The routing/ingestion images therefore haven't been rebuilt — the routing pod is frozen on d39a18d. This silently blocked the #73 instrumentation fix from deploying via CI.

Root cause

The gitea.d-ma.be → git.d-ma.be host rename left the Go module path stale. The ingestion image build dies at go mod download:

go: gitea.d-ma.be/mathias/mcp-chassis@v0.1.0: unrecognized import path
"gitea.d-ma.be/mathias/mcp-chassis": parse https://gitea.d-ma.be/mathias/mcp-chassis?go-get=1:
no go-import meta tags (meta tag git.d-ma.be/mathias/mcp-chassis did not match import path
gitea.d-ma.be/mathias/mcp-chassis)

The server now serves the go-import meta tag as git.d-ma.be/..., which no longer matches the requested gitea.d-ma.be/... import path. Local builds pass only because the module is cached; a clean CI build fetches fresh and fails.

Scope

  • mcp-chassis repo still declares module gitea.d-ma.be/mathias/mcp-chassis (its go.mod line 1).
  • ingestion/go.mod requires gitea.d-ma.be/mathias/mcp-chassis v0.1.0; imported in ingestion/cmd/server/main.go.
  • The top-level module (github.com/mathiasbq/supervisor, used by the routing image) has zero gitea.d-ma.be deps — so the routing image builds clean; only the ingestion build (run first in cd.yml) is affected.

Fix (cross-repo migration)

  1. mcp-chassis: rename module → git.d-ma.be/mathias/mcp-chassis, update internal imports, commit, tag v0.2.0 (check for other consumers first).
  2. ingestion: update import + go.mod require to the new path/tag, go mod tidy.
  3. Confirm cd.yml goes green; remove this workaround once CI builds both images again.

Interim

The #73 routing fix (da9bdc4) was deployed by building the routing image manually on koala (clean build, no mcp-chassis dep) and bumping the deployment tag — documented on #73. This issue tracks restoring the normal CI path and the ingestion image.

Refs: #73, #35, infra rename commit (fb58b25 in .context).

## Symptom `cd.yml` (Build and deploy) has failed on **every** commit since ~2026-06-26 (runs 288, 290, 292…). The routing/ingestion images therefore haven't been rebuilt — the routing pod is frozen on `d39a18d`. This silently blocked the #73 instrumentation fix from deploying via CI. ## Root cause The `gitea.d-ma.be → git.d-ma.be` host rename left the Go module path stale. The ingestion image build dies at `go mod download`: ``` go: gitea.d-ma.be/mathias/mcp-chassis@v0.1.0: unrecognized import path "gitea.d-ma.be/mathias/mcp-chassis": parse https://gitea.d-ma.be/mathias/mcp-chassis?go-get=1: no go-import meta tags (meta tag git.d-ma.be/mathias/mcp-chassis did not match import path gitea.d-ma.be/mathias/mcp-chassis) ``` The server now serves the go-import meta tag as `git.d-ma.be/...`, which no longer matches the requested `gitea.d-ma.be/...` import path. Local builds pass only because the module is cached; a clean CI build fetches fresh and fails. ## Scope - `mcp-chassis` repo still declares `module gitea.d-ma.be/mathias/mcp-chassis` (its `go.mod` line 1). - `ingestion/go.mod` requires `gitea.d-ma.be/mathias/mcp-chassis v0.1.0`; imported in `ingestion/cmd/server/main.go`. - The **top-level module** (`github.com/mathiasbq/supervisor`, used by the routing image) has **zero** `gitea.d-ma.be` deps — so the routing image builds clean; only the ingestion build (run first in `cd.yml`) is affected. ## Fix (cross-repo migration) 1. `mcp-chassis`: rename module → `git.d-ma.be/mathias/mcp-chassis`, update internal imports, commit, tag `v0.2.0` (check for other consumers first). 2. `ingestion`: update import + `go.mod` require to the new path/tag, `go mod tidy`. 3. Confirm `cd.yml` goes green; remove this workaround once CI builds both images again. ## Interim The #73 routing fix (`da9bdc4`) was deployed by building the routing image manually on koala (clean build, no mcp-chassis dep) and bumping the deployment tag — documented on #73. This issue tracks restoring the normal CI path and the ingestion image. Refs: #73, #35, infra rename commit (`fb58b25` in `.context`).
mathias commented 2026-06-30 19:41:00 +00:00
Author
Owner
Copy Link
Copy Source

Migration progress (2026-06-30)

  • mcp-chassis renamed module git.d-ma.be/mathias/mcp-chassis, tagged v0.2.0 (69d389d). Old v0.1.0 (old path) left intact so unmigrated consumers don't break.
  • ingestion (this repo) migrated to git.d-ma.be/mathias/mcp-chassis v0.2.0 + go mod tidy (b9d0331). Fresh go mod download now resolves; build + tests green. This is the fetch CI was failing on, so CD should go green again.

Other consumers — latent, not yet migrated

A repo-wide scan found two more importers of the old path. They still pin v0.1.0 (immutable tag, old module path) so they build from cache today, but each will fail the same go mod download the next time its image rebuilds from clean:

  • gitea-mcp — cmd/gitea-mcp/main.go + go.mod
  • tapir — internal/web/oidc/oidc.go (+ go.mod)

Both need the same one-line treatment: bump import + go.mod require to git.d-ma.be/mathias/mcp-chassis v0.2.0, go mod tidy. Worth doing proactively before their next deploy rather than discovering it red. (Out of scope for the #35 critical path; tracked here.)

## Migration progress (2026-06-30) - **mcp-chassis** renamed `module git.d-ma.be/mathias/mcp-chassis`, tagged **v0.2.0** (`69d389d`). Old `v0.1.0` (old path) left intact so unmigrated consumers don't break. - **ingestion** (this repo) migrated to `git.d-ma.be/mathias/mcp-chassis v0.2.0` + `go mod tidy` (`b9d0331`). Fresh `go mod download` now resolves; build + tests green. This is the fetch CI was failing on, so CD should go green again. ### Other consumers — latent, not yet migrated A repo-wide scan found two more importers of the old path. They still pin `v0.1.0` (immutable tag, old module path) so they build from cache today, but **each will fail the same `go mod download` the next time its image rebuilds from clean**: - `gitea-mcp` — `cmd/gitea-mcp/main.go` + `go.mod` - `tapir` — `internal/web/oidc/oidc.go` (+ go.mod) Both need the same one-line treatment: bump import + `go.mod` require to `git.d-ma.be/mathias/mcp-chassis v0.2.0`, `go mod tidy`. Worth doing proactively before their next deploy rather than discovering it red. (Out of scope for the #35 critical path; tracked here.)
mathias commented 2026-06-30 20:13:15 +00:00
Author
Owner
Copy Link
Copy Source

hyperguild CD restored (2026-06-30)

After the mcp-chassis v0.2.0 migration + ingestion bump (b9d0331), CD run 294 went green — first successful build since the rename. It built ingestion:b9d0331 + routing:b9d0331 and auto-bumped both infra deployment tags; flux rolled them out. The #73 routing fix reached prod through the normal CI path as intended.

Remaining (kept open under this issue): gitea-mcp and tapir still import the old gitea.d-ma.be/mathias/mcp-chassis path (pinned v0.1.0). They build from cache today but will hit the same go mod download failure on their next clean rebuild. Each needs the one-line bump to git.d-ma.be/mathias/mcp-chassis v0.2.0 + go mod tidy before its next deploy.

## hyperguild CD restored (2026-06-30) After the mcp-chassis v0.2.0 migration + ingestion bump (`b9d0331`), CD run **294 went green** — first successful build since the rename. It built `ingestion:b9d0331` + `routing:b9d0331` and auto-bumped both infra deployment tags; flux rolled them out. The #73 routing fix reached prod through the normal CI path as intended. Remaining (kept open under this issue): **gitea-mcp** and **tapir** still import the old `gitea.d-ma.be/mathias/mcp-chassis` path (pinned `v0.1.0`). They build from cache today but will hit the same `go mod download` failure on their next clean rebuild. Each needs the one-line bump to `git.d-ma.be/mathias/mcp-chassis v0.2.0` + `go mod tidy` before its next deploy.
mathias commented 2026-07-26 21:36:18 +00:00
Author
Owner
Copy Link
Copy Source

Already fixed by b9d0331 (fix(ingestion): migrate mcp-chassis import to git.d-ma.be path) — ingestion/go.mod now requires git.d-ma.be/mathias/mcp-chassis v0.2.0, imported in ingestion/cmd/server/main.go as chassisauth. CD (cd.yml) has been green on every push since run #318 (2026-07-09), confirmed via workflow_run_status. Closing.

Already fixed by b9d0331 (`fix(ingestion): migrate mcp-chassis import to git.d-ma.be path`) — `ingestion/go.mod` now requires `git.d-ma.be/mathias/mcp-chassis v0.2.0`, imported in `ingestion/cmd/server/main.go` as `chassisauth`. CD (`cd.yml`) has been green on every push since run #318 (2026-07-09), confirmed via `workflow_run_status`. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agent/ready
Meets the agent-ready contract; authorizes unattended execution
 blocked/client
Waiting on the client
 blocked/supplier
Waiting on a supplier
 blocked/upstream
Waiting on an upstream project or vendor
 risk/high
Irreversible, security-relevant, or control plane
 risk/low
Reversible, local, test-covered
 risk/medium
Touches shared state, deploys or data
 size/l
Too big - split it
 size/m
Under two days
 size/s
Under half a day
 size/xs
Under an hour
 status:dispatch
status:dispatched
status:review
status:reviewing
type/chore
Maintenance, no behaviour change
 type/decision
Human decision required; never agent/ready
 type/docs
Documentation only
 type/feat
New capability
 type/fix
Corrects broken behaviour
 type/ops
Infrastructure, deploy, runtime
 type/research
Investigate; output is a finding, not code
 type/test
Test coverage only
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
renovate-bot mathias
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mathias/hyperguild#74