[aw] AI Moderator: has stale lock file

Aperta Adatta ai principianti
  • Qualcosa non va?
#75,209 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
82/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, yaml
Ambito
ci-cd, devtools

Direzione di ricerca

Leggi .github/workflows/ai-moderator.md ed esamina i log «Check workflow lock file» dell’esecuzione collegata per i dettagli di [hash-debug]. Esegui gh aw compile per rigenerare il file di lock compilato, quindi convalidalo con gh aw compile --validate. Il lavoro è completato quando il file di lock corrisponde alla sorgente del workflow e la convalida ha esito positivo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows
What happened

AI Moderator has stale lock file.

View run #42080745147 · Workflow source · Previous failures

Branch: main

Next step

Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.

Failure details

[!WARNING]
Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

To fix, recompile the workflow:

gh aw compile

Then commit and push the updated .lock.yml file.

More ways to recompile

Using the gh-aw MCP server (if configured):

{
  "tool": "compile",
  "arguments": {
    "validate": true
  }
}

Recompile all workflows at once:

gh aw compile --all

Verify the result:

gh aw compile --validate
How to investigate the mismatch

The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

  • The raw frontmatter text that was used as input
  • Any imported files that were included in the hash
  • The canonical JSON that was fed to SHA-256
  • The resulting hash value

This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

gh aw add <path>@<exact-sha>
gh aw compile
How to disable this check

[!CAUTION]
Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

Set stale-check: false in the on: section of your workflow frontmatter:

on:
  issues:
    types: [opened]
  stale-check: false

After editing, recompile the workflow: gh aw compile

Copy a debugging prompt

Paste this into your coding agent:

Debug the agentic workflow "ai-moderator" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/github/gh-aw/actions/runs/42080745147

If the repository includes the agentic-workflows skill, load it before investigating.

Manage failure notifications

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

safe-outputs:
  report-failure-as-issue: false

This only disables issue reporting; it does not fix the failure.

Generated from AI Moderator · ◷

  • expires on Nov 6, 2026, 6:09 AM UTC
Lingua principale
Go
Stelle
5.6k
Fork
615
Merge medio
5h 36m
PR unite (30g)
805

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/gh-aw

Tutte le issue di github/gh-aw

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.