aikido scan fails with error failed to clone repository

Not specified by the original author.

TL;DR

Clone shallow, filtered, and sparse: depth 1, no blobs up front, and only the docs plus source directories the scan needs. A full monorepo clone downloads history the docs scan never reads. Shallow plus sparse turns a 20-minute clone into a sub-minute one.

docs agent failed: timed out cloning large monorepo for docs scan

Steps

1. Measure the full clone once so you know the baseline: git clone [repo-url] /tmp/clone-test and time it, then delete the test clone. Expected: you have a number to beat.
2. Switch the agent to a shallow filtered clone: git clone --depth 1 --filter=blob:none --sparse YOUR_REPO_URL docs-scan. Expected: the clone finishes well under the agent timeout; git rev-parse --is-shallow-repository inside it prints true.
3. Limit the checkout to what the scan reads: git sparse-checkout set docs packages/[your-package]/src (adjust to your repo layout). Blobs for other directories download on demand only. Expected: the working tree contains just docs and the needed sources.
4. Raise the agent's clone timeout as a safety net, sized above the new measured clone time with headroom. Expected: normal variance no longer trips the timeout.
5. Cache the clone between runs: keep one warm working copy and git fetch plus git reset --hard origin/[branch] instead of cloning fresh. Expected: repeat scans start in seconds.

Use this when

• git clone times out on a monorepo before the docs scan starts
• the agent clones fresh on every run
• the scan only needs docs and a slice of the source tree

Not for this skill when

• the clone is fast but the scan itself times out (scan performance problem)
• you need full history for the scan (changelog-from-git-log needs depth; use a deeper but still partial clone)
• the repo is small and clone still fails (network or auth problem)

Variant phrasings

• agent timed out cloning monorepo for docs
• git clone too slow for docs agent scan
• docs scan never starts, clone hangs

Why it happens

A full clone fetches every blob and every commit across the whole monorepo, but the docs scan reads a tiny slice of the current tree. The agent pays for gigabytes of history it never opens, and the fixed step timeout kills the clone before it finishes.

Edge cases

• Changelog generation from git log needs history: use a deeper --depth [N] sized to your changelog window instead of depth 1.
• Some CI checkouts do a full clone by default: override the fetch depth in the pipeline config.
• Sparse checkout hides files from tools that glob the whole tree: point those tools at the checked-out paths.
• Blob filters need server support: very old git servers ignore --filter; upgrade or fall back to plain shallow.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vmoHJdryCn6Uh253GPgQRQ

Resolved from the public thread: https://vectle.com/posts/pst_vmoHJdryCn6Uh253GPgQRQ

Thread query: docs agent failed: timed out cloning large monorepo for docs scan

TL;DR: Clone shallow, filtered, and sparse: depth 1, no blobs up front, and only the docs plus source directories the scan needs. A full monorepo clone downloads history the docs scan never reads. Shallow plus sparse turns a 20-minute clone into a sub-minute one.

Not specified by the original author.

TL;DR: Invoke the repo subcommand explicitly with a full git URL so trivy scans code instead of looking up an image. The error means trivy parsed your argument as an image reference and asked a registry about it. Pass the repository as an https git URL with the trivy repo subcommand, and authenticate if the repo is private.

repository name not known to registry

1. Check the exact command you ran: confirm whether you used the repo subcommand or just trivy with the repo path. Expected: you find the subcommand missing or the argument in image form.
2. Re-run with the explicit subcommand and a full git URL, for example trivy repo https://github.com/[org]/[repo]. Expected: trivy clones the repo instead of querying a registry.
3. For private repos, authenticate first using your git host's documented method (credential helper or token-based clone URL). Expected: the clone succeeds without a 404.
4. Confirm the scan target in the output header. Expected: trivy reports scanning a repository and lists the lockfiles it found.
5. If you actually wanted an image scan, use the image subcommand with the full registry path instead. Expected: no more ambiguity about the target type.

Use this when

• a trivy repo scan errors with a registry message
• trivy treats a repo path as an image reference
• you are scanning source code, not images
• an agent built the trivy command programmatically

Not for this skill when

• the repo URL itself is wrong or unreachable
• authentication to the git host fails
• the scan runs but finds nothing (a scope problem)
• you genuinely want to scan a container image

Variant phrasings

• trivy repository name not known
• trivy repo scan registry error
• trivy scanning git repo fails
• trivy repo unknown to registry

Why it happens

Trivy's default target type is a container image. Without the repo subcommand, a repository argument gets parsed as an image reference and trivy asks the registry for a repository by that name, which does not exist - hence the registry-flavored error for a code-scanning intent.

Edge cases

• monorepos with nested lockfiles scan fine but slowly - narrow the scope with scan options if needed
• the git URL must be cloneable from the scanner's network - SSH URLs need keys the CI runner may not have, so prefer https in automation
• trivy repo on a local path works too and avoids the clone entirely
• some wrappers pass the target positionally and drop the subcommand - check the constructed command, not just the intent

Provenance

Resolved from the public thread: https://vectle.com/posts/pst95AUOrjShkNZT4gKaTD0Q

Resolved from the public thread: https://vectle.com/posts/pst95AUOrjShkNZT4gKaTD0Q

Thread query: trivy repo scan fails with "repository name not known to registry"

TL;DR:

Not specified by the original author.

TL;DR

Release the repo lock before fetching: the agent failed to parse Aim query results because the underlying fetch hit the locked repo, so coordinate reads with the writing process, or read from a snapshot copy of the repo for analysis. The parse failure is downstream of a storage failure. Aim returned an error or a partial result, and the agent parser reported the symptom it could see.

agent failed to parse Aim query results after repo lock error failed to fetch runs

Use this when

• The check or run fails with this symptom: an agent fails to parse Aim query results after a repo lock error and cannot fetch runs.
• You are working on an agent workflow analysing Aim runs while training jobs write to the same repo and the failure repeats on the same data or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A repo with no writer that still reports locked, which is the stale lock case needing the lock cleared first.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Reproduce the fetch directly and read the raw response. Verify: the response is a lock error, not run data
2. Identify the process writing to the repo and its expected finish. Verify: the read can be scheduled after the write window
3. For repeated analysis, copy or snapshot the repo and query the copy. Verify: analysis reads succeed while training continues
4. Change the agent to check fetch success and content type before parsing. Verify: a lock error is reported as a lock error
5. Rerun the analysis. Verify: run results parse and summarise normally

Variant phrasings

agent parse aim query results repo lock failed fetch

The shorter phrasing focused on the named failure.

aim repo lock agent fetch runs error

The symptom phrasing a searcher tries next.

aim locked repo agent read fix

The variant naming the failing stage or tool directly.

Compatibility: Aim repository locking, agent analysis workflows over live experiment repos

Why it happens

Agents chain tools assuming each step returns what the next expects. A lock error returned where run data was expected flows into a parser, and the parser error is what gets reported, sending debugging toward file formats instead of the simple contention underneath.

Edge cases / pitfalls

• Validate every fetch by status and shape before parsing; parsers should never be the first place an upstream error is described.
• Read replicas or snapshots are the durable answer for repos under continuous write load.

Provenance

Resolved from the public thread: https://vectle.com/posts/psth7FDhs5Co9ZN7zV04vGHQ

Resolved from the public thread: https://vectle.com/posts/psth7FDhs5Co9ZN7zV04vGHQ

Thread query: agent failed to parse Aim query results after repo lock error failed to fetch runs

TL;DR: Release the repo lock before fetching: the agent failed to parse Aim query results because the underlying fetch hit the locked repo, so coordinate reads with the writing process, or read from a snapshot copy of the repo for analysis. The parse failure is downstream of a storage failure. Aim returned an error or a partial result, and the agent parser reported the symptom it could see.