542ed0afe3
Persistent agent memories now live in memory/ in this repo; the Claude auto-memory path is symlinked here so future memories land in the repo and get committed like any other change.
1.3 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| shared-recipe-checkout-race | Never run git checkout on ~/.abra/recipes/<recipe> on cc-ci while a CI build for that recipe is running — the harness chaos-deploys from that same working tree |
|
The cc-ci harness (run_recipe_ci.py) deploys the upgrade tier from the SHARED ~/.abra/recipes/<recipe> working tree on cc-ci via abra app deploy --chaos. Dev debugging that switches that checkout (git checkout -f, repro scripts) while a CI build runs makes CI deploy the wrong tree.
Why: immich builds 229/230 went RED with "bash: /pg_backup.sh: No such file or directory" — the configs stanza wasn't in the tree CI deployed, because concurrent dev repro scripts were flipping the same checkout between base tag and PR head. A faithful manual repro with no concurrent churn mounted the config fine.
How to apply: before triggering !testme, park the recipe checkout clean at the PR head and do zero abra/git activity on cc-ci for that recipe until the build verdicts. Also remember abra-chaos-deploy-checkout-gotcha (abra app new moves the checkout to the release tag). Related: drone-sqlite-log-extraction, immich-pgvectors-drop-database-panic