[aw-compat] Daily AW compat audit blocked: GitHub code search rate-limited (429) during repo discovery · Issue #70837 · github/gh-aw · GitHub
Skip to content

[aw-compat] Daily AW compat audit blocked: GitHub code search rate-limited (429) during repo discovery #70837

Open

Description

@github-actions

Summary

The daily cross-repo compilation/compatibility audit was blocked during Phase 1 (repository discovery) and could not proceed to cloning, compiling, or analysis. No compatibility findings exist for this run — this is a tooling/infrastructure report, not an audit result.

Phase reached

  • Phase 0 (build): completed. make build succeeded; binary built at gh-aw in the repo root.

    • Verified version: gh aw version b76697c
  • Phase 1 (discovery via GitHub code search): blocked. All search_code calls for gh-aw lock-file markers returned HTTP 429.

Blocker detail

gh CLI is unauthenticated in this environment (confirmed via gh auth status), so discovery used the GitHub MCP search_code tool instead, per environment constraints. That tool returned 429 on every attempt:

<b>Search attempts (1 original + 2 retries, policy limit reached)</b>
Query Result
"This file was automatically generated by gh-aw" filename:.lock.yml 429, retry-after approx 12.3s
same query, retried after 13s wait 429, retry-after approx 6.6s
"gh-aw-metadata" extension:lock.yml (materially different query, after 8s wait) 429, retry-after approx 0.96s

Per the audit policy (do not sleep or repeatedly retry; make at most one materially different retry, then stop), the run stopped after exhausting the allotted retry budget rather than continuing to poll a decaying rate-limit window.

Verified partial progress

  • make build completed successfully and produced a working gh-aw binary.
  • gh-aw --version confirmed as b76697c.
  • Environment constraint confirmed: gh CLI has no authenticated host, so GitHub reads must go through the MCP server tools.

What remains unverified

  • No candidate repositories were discovered, ranked, or selected.
  • No repositories were cloned.
  • No compile / fix --write / recompile passes were attempted.
  • No compatibility findings, codemod candidates, or syntax-error clusters exist for this run — do not treat the absence of findings as a clean result.

Suggested follow-up

  • Re-run the audit once the GitHub Search API rate limit for this token/integration has reset.
  • Consider whether concurrent workflow runs across the org are sharing and exhausting the same search rate-limit budget, and whether discovery should use a lower-cost query strategy (fewer, broader queries, or search_repositories instead of search_code where possible) to reduce 429 exposure.

Generated by 🔧 Daily AW Cross-Repo Compile Check · claude · agent · 61.1 AIC · ⌖ 0.816 AIC · ⊞ 6.6K · ◷

  • expires on Oct 28, 2026, 12:58 AM UTC-08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions