CI failure: gotosocial/main

[chloeobot]

Persistent CI failure from Containers CI Watchdog 2026-07-07.\n\nNote: the requested ci-failure label is missing and the labels API returned 404, so this issue was filed without the label.\n\n## gotosocial/main - goss-app-not-running - failing for 5 consecutive runs
Failure: GoToSocial panics on deprecated config and never reaches a passing Goss state.
Log excerpt

panic: value received for deprecated field 'instance-subscriptions-process-from', please use 'instance-subscriptions-process-cron' instead
Process: gotosocial: running:
Error: timeout of 1m0s reached before tests entered a passing state
Error response from daemon: No such container: dgoss-gotosocial-main

Suggested fix:

• Update containers-private/apps/gotosocial/ config/env from instance-subscriptions-process-from to instance-subscriptions-process-cron.
• Re-run the channel locally and keep the Goss process/HTTP checks only if startup no longer needs external state.
  Priority: medium

[chloeobot]

CI Watchdog 2026-07-09 update: still failing for 5 consecutive sampled runs.

Latest run: https://github.com/elfhosted/containers/actions/runs/29042824382

gotosocial/main -- goss-app-not-running -- failing for 5 consecutive runs

Failure: ttyd sidecar responds, but GoToSocial on port 8080 never accepts connections inside the dgoss timeout.
Log excerpt

http://localhost:8080: status: Error: Get "http://localhost:8080": dial tcp [::1]:8080: connect: connection refused
HTTP: http://localhost:3001: status: matches expectation: [200]
Error: timeout of 1m0s reached before tests entered a passing state
Error response from daemon: No such container: dgoss-gotosocial-main

Suggested fix

• Check apps/gotosocial/ci/goss.yaml and entrypoint startup requirements. If GoToSocial now needs external state or longer startup than dgoss allows, either set required test env or disable the runtime test for this channel.
  Priority: medium (runtime test failure)