recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

journal+status(redfix): M2 recon — discourse #4 (official-image) already !testme-green; mattermost #1 (pg-restore) triggered for verify
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-18 01:24:48 +00:00
parent 6771c713f0
commit abfbe8b0aa
2 changed files with 25 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
machine-docs/JOURNAL-redfix.md
View File

@ -268,3 +268,26 @@ Starting M2. Plan: recipe PRs (mattermost-lts, bluesky-pds, gitea) via the recip
(`!testme`-verified, never merge); harness fixes (keycloak collision-free canonical_domain + enroll;
mumble handshake stabilization) on a cc-ci branch; discourse overlay-scope decision. Node now mine
(Adversary done). Will examine the recipe-create-pr flow first, then execute one fix at a time.
## 2026-06-18T01:25Z — M2 recon: prior-phase fix PRs already exist for discourse + mattermost
Surveyed open PRs on all 6 mirrors before doing redundant work:
- **discourse #4** `discourse-official-image` ("switch to official discourse/discourse"): created
2026-06-16 by autonomic-bot; **!testme PASSED twice**, latest @53ba0910 today 16:36Z (run #849) ✅.
This migrates off deprecated bitnamilegacy → official image + drops sidekiq = EXACTLY what the
upgrade overlay asserts. So the overlay test was correctly demanding the migration; PR #4 IS the
discourse fix and is already !testme-green. (Reframes M1 "stale test": the test is right; the
release tag predates the migration; the fix is the migration PR, not weakening the test.)
- **mattermost-lts #1** `ci/pg-restore` ("reimport the postgres dump on restore"): correct
immich-pattern fix — pg_backup.sh (backup pg_dump|gzip; restore: terminate conns + DROP DATABASE
WITH FORCE + createdb + reimport) + dump-only `backup.volumes.postgres_data.path: backup.sql` +
`restore.post-hook: /pg_backup.sh restore`. Created 2026-05-30; needs a fresh !testme to confirm
green NOW. (Also PR #2 upgrade-2.1.11 overlaps — adds restore hook + version bump; #1 is the focused
fix.)
- mumble #1 = "cfold sweep probe" (not the fix — mumble is a harness flake, no recipe PR needed).
- bluesky #3 = version bump (not the routing fix — need a NEW PR for the app-alias collision).
- gitea, keycloak = no open PRs (gitea LFS #1 closed; keycloak is a harness fix).
M2 plan refined: VERIFY discourse #4 (re-!testme fresh) + mattermost #1 (!testme); CREATE recipe PRs
for bluesky (unique alias) + gitea (app.ini writable); HARNESS fixes for mumble (handshake stab) +
keycloak (collision-free canonical_domain + enroll). Starting with mattermost #1 !testme.

4
machine-docs/STATUS-redfix.md
View File

@ -82,12 +82,12 @@ deploys (Adversary done with M1).
| Recipe | Fix type | PR/branch | Status |
|---|---|---|---|
| mattermost-lts | recipe PR (pg_backup.sh + restore.post-hook) | — | starting |
| mattermost-lts | recipe PR (pg_backup.sh + restore.post-hook) | mirror PR #1 `ci/pg-restore` (exists, correct) | !testme triggered @01:24Z — verifying restore green |
| bluesky-pds | recipe PR (unique internal alias for caddy→app) | — | pending |
| gitea | recipe PR (app.ini → writable volume) | — | pending |
| keycloak | harness (collision-free canonical_domain) + enroll | — | pending |
| mumble | harness (handshake readiness/retry stabilization) | — | pending |
| discourse | overlay-scope test PR + upstream issue (decide) | — | pending |
| discourse | recipe PR (official-image migration) | mirror PR #4 `discourse-official-image` | already !testme-GREEN @53ba0910 (run #849, 16:36Z); re-verify fresh |
## Gate: M1 — PASS (above). M2 not yet claimed.