Drop the brencher-state-proxy sidecar from hermes_infra -- it is
no longer needed. The sidecar existed to relay /state from
brencher.rudolf.keenetic.link into the admin overlay; that relay is
unnecessary since brencher ingress handles the path itself.
Changes vs the brencher-state-proxy commit that was merged in #4:
- delete hermes_squid/brencher-state-proxy.conf
- remove the brencher-state-proxy: service block from
hermes_squid/stack-compose.yml
- remove the brencher_state_proxy_conf: top-level config object
- drop brencher-state-proxy from the NO_PROXY / no_proxy lists
- update the surrounding comments
The built-in act_runner cache-server binds to an interface unreachable
from per-job container networks (default container.network: ""), so
ACTIONS_CACHE_URL resolves to 192.168.112.21:37051 and every job burns
~9 minutes on:
::warning::Failed to save: reserveCache failed: connect ETIMEDOUT
::warning::Failed to restore: getCacheEntry failed: connect ETIMEDOUT
Measured on PR #15 in admin/brencher (gitea/actions/runs/16):
each of 3 jobs ≈12 min wall-clock, of which 9 min is dead air waiting
for cache timeouts.
Run a dedicated act_runner cache-server on the same overlay network and
point the runner at it via external_server. secret shared via
ACT_RUNNER_EXTERNAL_SECRET env on both services.
Related: admin/brencher#15 (whose python-package.yml enables cache:'pip'
but currently gets no benefit because the cache backend is unreachable).
Refs: gitea/actions/runs/16 (job #248 logs)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
x
The built-in act_runner cache-server binds to an interface unreachable from per-job container networks (default container.network: ""), so ACTIONS_CACHE_URL resolves to 192.168.112.21:37051 and every job burns ~9 minutes on: ::warning::Failed to save: reserveCache failed: connect ETIMEDOUT ::warning::Failed to restore: getCacheEntry failed: connect ETIMEDOUT Measured on PR #15 in admin/brencher (gitea/actions/runs/16): each of 3 jobs ≈12 min wall-clock, of which 9 min is dead air waiting for cache timeouts. Run a dedicated act_runner cache-server on the same overlay network and point the runner at it via external_server. secret shared via ACT_RUNNER_EXTERNAL_SECRET env on both services. Related: admin/brencher#15 (whose python-package.yml enables cache:'pip' but currently gets no benefit because the cache backend is unreachable). Refs: gitea/actions/runs/16 (job #248 logs)Pull request closed