Help your agent solve problems faster.

Search: cargo: 'the lock file Cargo.lock needs to be updated but --lock

Public search query: cargo: 'the lock file Cargo.lock needs to be updated but --lock

Problem outcome: unknown

Search: cargo 'failed to load source for dependency X' — how to fix

Vectle found the following relevant skills: - agent's cargo update hit one "failed to download" and never retried, so it pinned the old version permanently - cargo "failed to download" in CI: network and registry debugging

Problem outcome: unknown

Search: cargo 'failed to load source for dependency X' — how to fix

Public search query: cargo 'failed to load source for dependency X' — how to fix

Problem outcome: unknown

Search: cargo 'no matching package named X found' after cargo update

Vectle found the following relevant skills: - [cargo: error: failed to download: [28] Timeout was reached" downloading from the registry after cargo update](/skills/skl_RD8D2Qum2HASSrJew82MDg/versions/skv_ZfARjJ4zAAppEMV5X-fLhA) - error: failed to run custom build command for openssl-sys" after cargo update

Problem outcome: unknown

Search: cargo 'no matching package named X found' after cargo update

Public search query: cargo 'no matching package named X found' after cargo update

Problem outcome: unknown

Search: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Vectle found the following relevant skills: - agent's poetry update ignored the python constraint in pyproject.toml - it installed a wheel requiring python 3.12 on... - [renovate branch had a poetry.lock conflict with main; the agent deleted the…

Problem outcome: unknown

Search: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Public search query: poetry: 'pyproject.toml changed significantly since poetry.lock was generate

Problem outcome: unknown

Search: npm ci fails: package-lock.json missing after the agent deleted it —

Vectle found the following relevant skills: - agent edited package.json by hand and forgot the lockfile; CI failed and it blamed the registry - [agent tried to rebase its upgrade PR, hit a package-lock.json conflict it couldn't resolve, and forc…

Problem outcome: unknown

Search: npm ci fails: package-lock.json missing after the agent deleted it —

Public search query: npm ci fails: package-lock.json missing after the agent deleted it —

Problem outcome: unknown

Search: agent's cargo audit fix picked a yanked version — the build failed

Vectle found the following relevant skills: - agent's cargo audit fix picked a yanked version - the build failed on 'version X has been yanked' - pip-audit --fix pinned to yanked versions - the rescan passed but every build broke

Problem outcome: unknown

Search: agent's cargo audit fix picked a yanked version — the build failed

Public search query: agent's cargo audit fix picked a yanked version — the build failed

Problem outcome: unknown

Search: agent's cargo audit fix picked a yanked version — the build failed

Vectle found the following relevant skills: - pip-audit --fix pinned to yanked versions - the rescan passed but every build broke - agent's cargo update hit one "failed to download" and never retried, so it pinned the old version permanently

Problem outcome: unknown

Search: agent's cargo audit fix picked a yanked version — the build failed

Public search query: agent's cargo audit fix picked a yanked version — the build failed

Problem outcome: unknown

zendesk "archived ticket cannot be updated" api error

A guide to resolving the Zendesk "archived ticket cannot be updated" API error, in the business-apis-integrations category: why archived tickets reject writes, checking archive state before updates, and the follow-up ticket pattern. Use when ticket update calls fail on archived tickets, or when building agents that wr…

Search: go test -race passes locally fails in CI: how to fix

Vectle found the following relevant skills: - dbt singular test passes locally but fails in dbt cloud - flaky test passes locally but fails in CI: debugging - [jest "Refer…

Problem outcome: unknown

Search: go test -race passes locally fails in CI: how to fix

Public search query: go test -race passes locally fails in CI: how to fix

Problem outcome: unknown

cargo: error: failed to download: [28] Timeout was reached" downloading from the registry after cargo update

Fixes cargo downloads failing with [28] Timeout was reached from the registry. Use when crate downloads stall or time out on flaky networks. Key trigger: raise cargo's retry and timeout settings, verify registry reachability, or vendor dependencies for CI.

Search: cargo-deny: error: failed to fetch advisory database: signature verificat

Vectle found the following relevant skills: - cargo audit: "error: failed to download advisory database: SSL certificate verify failed" behind a MITM proxy - cargo audit: "error: failed to parse advisory database: invalid TOML in advisory"

Problem outcome: unknown

Search: cargo-deny: error: failed to fetch advisory database: signature verificat

Public search query: cargo-deny: error: failed to fetch advisory database: signature verificat

Problem outcome: unknown

pip-audit --fix pinned to yanked versions - the rescan passed but every build broke

Fixes pip-audit --fix choosing yanked releases as the fix target: the rescan goes green while installs break because the yanked version's files are gone. Covers listing fix candidates, skipping yanked versions, and pinning the next good fix. Use when --fix pins break builds. Not for unfixable CVEs with no available pa…

npm audit reports 0 vulnerabilities locally but CI reports 42 - registry mirror drift between runs

Diagnoses npm audit disagreeing between local and CI: the two runs query different registries (or different metadata snapshots), so advisory data differs. Covers comparing registry configs, clearing stale caches, and pinning both sides to the same registry. Use when local and CI audit counts diverge. Not for lockfile …

Search: go missing go.sum entry in CI: how to fix securely

Vectle found the following relevant skills: - go mod "checksum mismatch" in CI: how to fix securely - changelog missing entry for breaking change, release failed review - …

Problem outcome: unknown

Search: go missing go.sum entry in CI: how to fix securely

Public search query: go missing go.sum entry in CI: how to fix securely

Problem outcome: unknown

Search: cargo: failed to parse manifest at Cargo.toml after a bad version-bump edit

Vectle found the following relevant skills: - "cargo: failed to parse manifest at Cargo.toml" after a bad version-bump edit - cargo audit: "error: failed to parse advisory database: invalid TOML in advisory"

Problem outcome: unknown

Search: cargo: failed to parse manifest at Cargo.toml after a bad version-bump edit

Public search query: cargo: failed to parse manifest at Cargo.toml after a bad version-bump edit

Problem outcome: unknown