Cryptograss:Moods/emergence/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/183 |
Merge with Justin's edit: cron-health runs again, token and dumps done, podcast import held, staging copy pending (via update-page on MediaWiki MCP Server) |
||
| Line 2: | Line 2: | ||
<todo> | <todo> | ||
- task: " | - task: "Look at why the nightly podcast import wants to change 240 pages, then release it or fix it" | ||
who: justin | who: justin | ||
kind: | kind: review | ||
link: "https:// | link: "https://pickipedia.xyz/status/podcast-import.txt" | ||
note: " | note: "Held by its change budget (limit 50): 240 updates, 0 new, mostly Picky Fingers (80) and What's The Reason (78). Unknown how many nights it has been held, because cron-health could not run from 4 September until today. If the changes are intended, re-run with --max-changes 240." | ||
- task: "Drop or refresh the staging database on hunter (magenta-staging-pg): it is a pre-redaction copy" | |||
- task: " | who: magent | ||
who: | kind: cleanup | ||
kind: | note: "Restored 2026-09-28, before the 2026-10-04 redaction; 74 messages there still hold an unredacted PGPASSWORD. Its web view on justin1.hunter is down, so it isn't public. Waiting on Justin's yes, since it is the style-iteration staging." | ||
- task: "Say whether the 2025 Porcupine stub secrets were ever registered on a deployed claim contract" | - task: "Say whether the 2025 Porcupine stub secrets were ever registered on a deployed claim contract" | ||
who: justin | who: justin | ||
kind: check | kind: check | ||
note: "The leaked value came from a local dev build on 2025-06-11 (token 1). If those secrets were never registered on a live contract, there is nothing to do." | note: "The leaked value came from a local dev build on 2025-06-11 (token 1). If those secrets were never registered on a live contract, there is nothing to do." | ||
- task: "Decide the memory commitment's open questions (salt key, who commits, first edition)" | - task: "Decide the memory commitment's open questions (salt key, who commits, first edition)" | ||
who: justin | who: justin | ||
kind: decision | kind: decision | ||
link: "Cryptograss:Memory commitment" | link: "Cryptograss:Memory commitment" | ||
- task: "Merge maybelle-config#183 and deploy maybelle, so cron-health compiles again" | |||
who: justin | |||
link: "https://github.com/cryptograss/maybelle-config/pull/183" | |||
done: 2026-10-10 | |||
note: "Build 48100 ran every stage for the first time since 4 September." | |||
- task: "Delete the pre-redaction dumps on hunter" | |||
who: magent | |||
done: 2026-10-10 | |||
note: "All three shredded once cron-health showed maybelle's memory-lane backups fresh." | |||
- task: "Revoke old GitHub tokens" | |||
who: justin | |||
done: 2026-10-10 | |||
note: "One token on magent-cryptograss, matching the one in use (classic, no expiry, nine scopes). Worth giving its replacement an expiry date some day." | |||
- task: "Deploy maybelle after the database password rotation" | - task: "Deploy maybelle after the database password rotation" | ||
who: justin | who: justin | ||
Revision as of 19:22, 10 October 2026
What people in the magent-self Mood have been left to do. Kept by magent; anyone may tick an item.
- ☐Look at why the nightly podcast import wants to change 240 pages, then release it or fix itHeld by its change budget (limit 50): 240 updates, 0 new, mostly Picky Fingers (80) and What's The Reason (78). Unknown how many nights it has been held, because cron-health could not run from 4 September until today. If the changes are intended, re-run with --max-changes 240.
- ☐Drop or refresh the staging database on hunter (magenta-staging-pg): it is a pre-redaction copyRestored 2026-09-28, before the 2026-10-04 redaction; 74 messages there still hold an unredacted PGPASSWORD. Its web view on justin1.hunter is down, so it isn't public. Waiting on Justin's yes, since it is the style-iteration staging.
- ☐Say whether the 2025 Porcupine stub secrets were ever registered on a deployed claim contractThe leaked value came from a local dev build on 2025-06-11 (token 1). If those secrets were never registered on a live contract, there is nothing to do.
- ☐
Done (8)
- ☑Merge maybelle-config#183 and deploy maybelle, so cron-health compiles againBuild 48100 ran every stage for the first time since 4 September.
- ☑Delete the pre-redaction dumps on hunterAll three shredded once cron-health showed maybelle's memory-lane backups fresh.
- ☑Revoke old GitHub tokensOne token on magent-cryptograss, matching the one in use (classic, no expiry, nine scopes). Worth giving its replacement an expiry date some day.
- ☑Deploy maybelle after the database password rotation
- ☑Rotate the Blue Railroad bot password
- ☑Rotate the PickiPedia database passwordTook the wiki down 18:17–18:48Z. Two causes, both fixed: secrets written after the step that needs them (maybelle-config#181), and secrets emitted in PHP double quotes, which mangled a $ in the new password (#182).
- ☑Rotate the delivery-kid key and the wiki's $wgSecretKey
- ☑Rotate Alchemy, Jenkins admin, memory-lane SECRET_KEY, code-server, GlitchTip admin