gabriel / musehub public
fix BREAKING fix/clone-url-and-fetch-timeout #1 / 1
AI Agent gabriel · 71 days ago · Apr 10, 2026 · Diff

fix: clone URL shows muse clone https:// and nginx fetch timeout 504

Bug 1: Repo home page sidebar showed 'muse remote add local musehub://owner/slug' - Wrong command (should be 'muse clone') - Wrong scheme (muse CLI does not understand musehub://, only http/https) - Hardcoded host (always showed musehub.ai even on staging)

Fix: ui_repo.py now passes clone_url built from request.base_url so it adapts to any host automatically. Service layer and MCP executor use settings.public_url (overridable via PUBLIC_URL env var). Template shows 'muse clone <url>'. Dead initCloneTabs/initCopyClone TS code removed.

Bug 2: 'muse clone' on large repos returned HTTP 504 — nginx gave only 60s to /fetch and /fetch/objects endpoints (location / default), but streaming all object bytes for a large repo easily exceeds that.

Fix: Added dedicated location block for fetch endpoints with 300s timeout, matching the existing push block.

Also adds settings.public_url field, deploy/ to Dockerfile and override bind-mount, and regression tests covering both bugs.

sha256:70fd807bda25cfacab9b301bc7be6ab01b27844b080454ac0eba25ea3657c7eb sha
sha256:a4fa1ae5239b2857334e47bae25dc38150e52094467b8fca8543b8093fd2b650 parent
sha256:92b919ead5b986bcc4656fad013f402f291144a2ea660299851f70ee6ad14d19 snapshot
← Older Oldest on fix/clone-url-and-fetch-timeout
All commits
Newer → Latest on fix/clone-url-and-fetch-timeout

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:70fd807bda25cfacab9b301bc7be6ab01b27844b080454ac0eba25ea3657c7eb --body "your comment"