molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 14 Actions 2 Packages Projects Releases Wiki Activity

install_plugin: gitea:// source on a PRIVATE repo hangs → 502 (no fast-fail; never reconciles) #3108

New Issue
Closed
opened 2026-06-21 05:56:09 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-21 05:56:09 +00:00
Member
Copy Link
Copy Source

Summary: install_plugin with a gitea://owner/repo#ref source pointing at a private Gitea repo hangs and returns HTTP 502 (CloudFlare gateway timeout, ~100s) instead of fast-failing. The workspace is never reconciled/restarted (the POST hangs before that), and the install does not persist.

Repro (observed live 2026-06-21):

  1. install_plugin(workspace=<id>, source="gitea://molecule-ai/molecule-ai-plugin-image-gen#v0.1.0") where the repo was private.
  2. Result: HTTP 502 (host agents-team.moleculesai.app). Two attempts, both 502. list_installed_plugins stayed empty; target workspace uptime kept climbing (never restarted) → the handler failed/hung early, before touching the box.
  3. Workaround that fixed it: making the repo public → the exact same install returned {"status":"installed"} immediately and reconciled the workspace.

Root cause (strongly indicated): the server-side POST /workspaces/:id/plugins gitea source resolver fetches the repo in a way that hangs on a private repo (e.g. an unauthenticated git clone that blocks on a credential prompt, or an auth path that retries until the gateway times out) rather than using an authenticated Gitea archive/tarball API call that returns a clean 401/403/404. Note platform-mcp (also private) installs fine because it's delivered via the core-declared concierge path, not the gitea:// user-install resolver — so the bug is specific to the gitea:// install_plugin code path.

Impact: any private-repo plugin installed via gitea:// (the marketplace/user-install path) 502s with no actionable error. Operators can't tell "private repo" from "install pipeline broken."

Suggested fix:

  • Resolve gitea:// sources via the authenticated Gitea API (archive/tarball or contents) with the resolver's token, so a private repo the token can read works, and one it can't returns a fast, clear 403/404 (not a hang).
  • Bound the install op with a timeout well under the gateway's, returning a structured error.
  • Surface a clear "repo not accessible / private" error to install_plugin callers.

Found while shipping the image-gen plugin (RFC #3105). Filed for the plugin-install pipeline owners.

**Summary:** `install_plugin` with a `gitea://owner/repo#ref` source pointing at a **private** Gitea repo **hangs and returns HTTP 502** (CloudFlare gateway timeout, ~100s) instead of fast-failing. The workspace is never reconciled/restarted (the POST hangs before that), and the install does not persist. **Repro (observed live 2026-06-21):** 1. `install_plugin(workspace=<id>, source="gitea://molecule-ai/molecule-ai-plugin-image-gen#v0.1.0")` where the repo was **private**. 2. Result: `HTTP 502` (host `agents-team.moleculesai.app`). Two attempts, both 502. `list_installed_plugins` stayed empty; target workspace uptime kept climbing (never restarted) → the handler failed/hung **early**, before touching the box. 3. **Workaround that fixed it:** making the repo **public** → the exact same install returned `{"status":"installed"}` immediately and reconciled the workspace. **Root cause (strongly indicated):** the server-side `POST /workspaces/:id/plugins` gitea source resolver fetches the repo in a way that **hangs on a private repo** (e.g. an unauthenticated `git clone` that blocks on a credential prompt, or an auth path that retries until the gateway times out) rather than using an **authenticated Gitea archive/tarball API call** that returns a clean 401/403/404. Note `platform-mcp` (also private) installs fine because it's delivered via the core-declared concierge path, **not** the `gitea://` user-install resolver — so the bug is specific to the `gitea://` install_plugin code path. **Impact:** any private-repo plugin installed via `gitea://` (the marketplace/user-install path) 502s with no actionable error. Operators can't tell "private repo" from "install pipeline broken." **Suggested fix:** - Resolve `gitea://` sources via the **authenticated Gitea API** (archive/tarball or contents) with the resolver's token, so a private repo the token *can* read works, and one it *can't* returns a fast, clear 403/404 (not a hang). - Bound the install op with a timeout well under the gateway's, returning a structured error. - Surface a clear "repo not accessible / private" error to `install_plugin` callers. Found while shipping the image-gen plugin (RFC #3105). Filed for the plugin-install pipeline owners.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#3108
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?