Krow/krow_backend
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record the CI runner, now that one exists
Some checks failed
CI / test (push) Failing after 6m25s
Details
CI / fixture (push) Failing after 47s
Details

Browse Source 
Both repositories carried GitHub Actions workflows on a Gitea remote and
nobody had confirmed a runner. There was not one: the 924 frontend checks,
the whole Go suite, the skip guard and the suite-shrank guard had never run
on a push, only when somebody remembered.

gitea/act_runner v0.6.1 is registered as krow-runner on the cluster host. This
commit is also the first push that can prove it picks up a job, which is the
failure mode worth catching — a runner that registers and never runs anything
looks identical to a healthy one in the Runners list.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJvibeSc1JYXjatankqM1g
This commit is contained in:
Suriyakumarvijayanayagam
2026-08-31 11:13:47 +05:30
parent 109fc2f1c6
commit fd1812e161
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/handover.md
View File

@@ -174,9 +174,17 @@ course, not a position in a window.
CI against the target database" is still aspirational. CI against the target database" is still aspirational.
- The fixture-drift CI jobs need `FRONTEND_REPO_TOKEN` to see the sibling repo, - The fixture-drift CI jobs need `FRONTEND_REPO_TOKEN` to see the sibling repo,
and fail rather than pass quietly without it. and fail rather than pass quietly without it.
- The remote is Gitea. These are GitHub Actions workflows; they do nothing until - The remote is Gitea and the workflows are GitHub Actions syntax. Gitea Actions
a compatible runner exists. Nobody has confirmed a runner exists, so treat runs them, and a runner now exists: `gitea-runner` (gitea/act_runner v0.6.1)
both repositories as having no CI until somebody checks. on the cluster host, registered as `krow-runner` with labels
`ubuntu-latest, ubuntu-22.04` mapped to `node:20-bookworm`. Before that, both
repositories had workflows that had never executed once — the 924 frontend
checks, the whole Go suite, the skip guard and the suite-shrank guard were
all things somebody had to remember to run.
If a job fails resolving `actions/checkout` or `actions/setup-node`, the
runner needs egress to github.com or a mirror; that is where those actions
come from and Gitea does not host them.
- **The application talks to its database in clear text.** `DATABASE_SSLMODE= - **The application talks to its database in clear text.** `DATABASE_SSLMODE=
disable` against `66.116.207.225`, which is a DIFFERENT machine from the disable` against `66.116.207.225`, which is a DIFFERENT machine from the
cluster host — so credentials and every row cross the network unencrypted. cluster host — so credentials and every row cross the network unencrypted.