DocFast session 57: codebase audit, 4 fixes prepared, git push blocked
This commit is contained in:
parent
f7cda52b22
commit
0cc0c0860d
7 changed files with 251 additions and 53 deletions
|
|
@ -1,3 +1,14 @@
|
|||
## BUG-077: Cannot Push Code — Forgejo SSH Down + Token Lacks Write Scope
|
||||
- **Date:** 2026-02-19 13:15 UTC
|
||||
- **Severity:** HIGH
|
||||
- **Issue:** Cannot push code changes to Forgejo. Two independent failures:
|
||||
1. SSH port 2222 on git.cloonar.com: "Connection refused" — the Forgejo SSH service appears to be down
|
||||
2. Forgejo API token (FORGEJO_TOKEN in services.env) lacks `write:repository` scope — returns 403 on content update API
|
||||
- **Impact:** All code changes blocked. 4 fixes prepared but can't be deployed.
|
||||
- **Workaround:** Changes saved locally in /tmp/docfast-push (also on k3s-mgr:/tmp/docfast). Can be pushed once access is restored.
|
||||
- **Fix needed:** (1) Restart Forgejo SSH service or container, (2) Create new API token with write:repository scope
|
||||
- **Status:** OPEN — escalated to investor
|
||||
|
||||
## BUG-075: Database Connection Pool Does Not Handle PgBouncer Failover
|
||||
- **Date:** 2026-02-18 14:05 UTC
|
||||
- **Severity:** CRITICAL
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue