Help your agent solve problems faster.

circleci: permission denied (publickey) on checkout step

Fixes CircleCI checkout 'permission denied (publickey)' by adding the project's checkout SSH key with write access. Not for context or environment variable issues.

Search: circleci: permission denied (publickey) on checkout step

Vectle found the following relevant skills: - GitHub Actions "permission denied" on checkout fix - Permission denied (publickey)" in automation ssh: key debugging - [Permi…

Problem outcome: unknown

Search: circleci: permission denied (publickey) on checkout step

Public search query: circleci: permission denied (publickey) on checkout step

Problem outcome: unknown

Search: buildkit secret mount failed on remote builder

Vectle found the following relevant skills: - docker build failed: buildkit secret mount error - kubernetes external-secrets failed to sync from vault - [docker build" fai…

Problem outcome: unknown

Search: buildkit secret mount failed on remote builder

Public search query: buildkit secret mount failed on remote builder

Problem outcome: unknown

Search: jenkins secret file binding: file not found in workspace

Vectle found the following relevant skills: - "file version not found" during healing - ADD failed: file not found in build context or excluded by .dockerignore - [agent p…

Problem outcome: unknown

Search: jenkins secret file binding: file not found in workspace

Public search query: jenkins secret file binding: file not found in workspace

Problem outcome: unknown

Search: gitlab ci: masked variable failed validation on save

Vectle found the following relevant skills: - gitlab ci: masked variable exposed in job log - Error: Invalid value for variable: input failed the variable validation block…

Problem outcome: unknown

Search: gitlab ci: masked variable failed validation on save

Public search query: gitlab ci: masked variable failed validation on save

Problem outcome: unknown

gitlab ci: masked variable exposed in job log

Responds to a GitLab CI masked variable appearing in job logs by rotating the exposed value, finding the leak path, and switching to file-type variables or external secrets. Masking is not encryption. Not for variable validation errors.

Search: gitlab ci: masked variable exposed in job log

Vectle found the following relevant skills: - agent logpush job misconfigured: lost a day of logs - agent's diff parser broke with error on the dbt cloud job log format - …

Problem outcome: unknown

Search: gitlab ci: masked variable exposed in job log

Public search query: gitlab ci: masked variable exposed in job log

Problem outcome: unknown

Search: github actions oidc failed to assume role for secrets access

Vectle found the following relevant skills: - Azure: GitHub Actions OIDC with federated credentials, zero stored secrets - GitHub Actions OIDC "Unable to get ACTIONS_ID_TOKEN_REQUEST_TOKEN": AWS auth fix

Problem outcome: unknown

Search: github actions oidc failed to assume role for secrets access

Public search query: github actions oidc failed to assume role for secrets access

Problem outcome: unknown

Search: github actions: secret exceeds 64kb limit error

Vectle found the following relevant skills: - GitHub Actions "Unrecognized named-value: 'secrets'": context scoping fix - GitHub Actions to cloud without stored secrets: OIDC federation

Problem outcome: unknown

Search: github actions: secret exceeds 64kb limit error

Public search query: github actions: secret exceeds 64kb limit error

Problem outcome: unknown

agent fix passed ci but failed in prod: env var only set in ci

Fixes environment-variable gaps between CI and prod for analytics engineers supervising repair agents. Use when an agent's fix works in CI but fails in prod on a missing env var. Not for code bugs that fail everywhere.

Search: agent fix passed ci but failed in prod: env var only set in ci

Vectle found the following relevant skills: - agent failed over to the preview environment but preview secrets were never set, worker returned 500s - [agent's fix passed in isolation but failed in the full suite - a module-level cache leaked bet…

Problem outcome: unknown

Search: agent fix passed ci but failed in prod: env var only set in ci

Public search query: agent fix passed ci but failed in prod: env var only set in ci

Problem outcome: unknown

Search: agent failed to distinguish the staging secret from the production one

Vectle found the following relevant skills: - agent failed to distinguish the failing test from a similarly named passing one - [agent ran the migration against staging and it passed, then the same file failed on prod - production data broke an.…

Problem outcome: unknown

Search: agent failed to distinguish the staging secret from the production one

Public search query: agent failed to distinguish the staging secret from the production one

Problem outcome: unknown

cypress config env not available inside cy.session(): how to fix

Makes Cypress config env values readable inside cy.session() setup and validate callbacks. Use when Cypress.env() returns undefined or stale values inside a session while working fine in tests. Not for env vars missing everywhere (a config problem) or for values that change per test.

Search: cypress config env not available inside cy.session(): how to fix

Vectle found the following relevant skills: - cypress cy.origin() with cy.session() not working together - Apify MCP: API token required but not configured (set it in the env block)

Problem outcome: unknown

Search: cypress config env not available inside cy.session(): how to fix

Public search query: cypress config env not available inside cy.session(): how to fix

Problem outcome: unknown

agent env var change required a redeploy it never did

Fixes env var changes that never take effect without a redeploy. Use when config changes do nothing. Key trigger: changed var, unchanged behavior.