multica

mirror of https://github.com/multica-ai/multica.git synced 2026-07-05 21:39:54 +02:00

Files

LinYushen a6e8ae964e fix(skills): handle GitHub API 403 / rate limit during skill import (#2215 )

Importing a skill from a github.com URL probes the commits API to
disambiguate slash-bearing refs. On self-hosted servers the IP is often
already over GitHub's 60-req/hour unauthenticated limit, so the very
first probe returns 403 and the previous code aborted the entire
import ("validating ref \"main/skills/pptx\": github API returned
status 403").

Two changes make this resilient:

* Forward GITHUB_TOKEN as a bearer token on every api.github.com request
  via a new doGitHubAPIGet / addGitHubAuthHeader helper. With a token,
  the limit becomes 5000 req/hour and the issue disappears entirely.
* When the API still returns 401/403/429 (no token, or limit exhausted
  on the higher tier) treat the probe as indeterminate via
  errGitHubAPIBlocked, keep trying remaining candidates, and finally
  fall back to parseGitHubURL's optimistic single-segment split. This
  covers the common case (single-word refs like "main") even when the
  API is fully blocked. A warn log points operators at GITHUB_TOKEN.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-05-07 16:28:34 +08:00

cmd

perf(heartbeat): batch runtime last_seen_at writes (#2213 )

2026-05-07 15:50:27 +08:00

internal

fix(skills): handle GitHub API 403 / rate limit during skill import (#2215 )

2026-05-07 16:28:34 +08:00

migrations

chore(db): drop unused agent_task_queue.last_heartbeat_at (#2212 )

2026-05-07 15:45:29 +08:00

pkg

perf(heartbeat): batch runtime last_seen_at writes (#2213 )