CI failure: mediastorm/main - upstream-rebase

[chloeobot]

mediastorm/main - upstream-rebase - failing for 5 consecutive runs

Failure: 02-domain-proxy.patch no longer applies against upstream backend/main.go:22.
Log excerpt

#21 0.068 Applying /patches/01-preset-defaults.patch...
#21 0.073 Applying /patches/02-domain-proxy.patch...
#21 0.076 error: patch failed: backend/main.go:22
#21 0.076 error: backend/main.go: patch does not apply
#21 ERROR: process "/bin/sh -c cd /source && for p in /patches/*.patch; do echo \"Applying $p...\" && git apply \"$p\" || exit 1; done" did not complete successfully: exit code: 1

Suggested fix

• Rebase containers-private/apps/mediastorm/patches/02-domain-proxy.patch against godver3/mediastorm tag v1.5.0-20260709.
• Check upstream changes around backend/main.go:22 before replaying the rest of the patch stack.
  Priority: high

Label note: ci-failure could not be attached because GitHub returned could not add label: 'ci-failure' not found and label creation returned HTTP 404.

[chloeobot]

Latest watchdog update: mediastorm/main is still failing, now seen in 5 consecutive scheduled runs in the current sample.

Latest variant:

#21 0.069 Applying /patches/01-preset-defaults.patch...
#21 0.074 Applying /patches/02-domain-proxy.patch...
#21 0.077 error: patch failed: backend/main.go:25
#21 0.078 error: backend/main.go: patch does not apply

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

Label note: ci-failure still cannot be created or attached. GitHub returned HTTP 404: Not Found for label creation, and could not add label: ci-failure not found when attempting issue creation with the label.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.