Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Implicitly cleaning up <TemporaryDirectory '/tmp/tmpgdn6nea5'>

The HMAC key is 10 bytes long, which is below the minimum recommended length of 32 bytes for SHA256. See RFC 7518 Section 3.2.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

`verify=<str>` is deprecated. Use `verify=ssl.create_default_context(cafile=...)` or `verify=ssl.create_default_context(capath=...)` instead.

The HMAC key is 10 bytes long, which is below the minimum recommended length of 32 bytes for SHA256. See RFC 7518 Section 3.2.

Error: invalid configuration: receivers::otlp: must specify at least one protocol when using the OTLP receiver

{"level":"warn","ts":1774452392.4541955,"caller":"grpc@v1.54.0/clientconn.go:1292","msg":"[core][Channel #10 SubChannel #11] grpc: addrConn.createTransport failed to connect to {\n \"Addr\": \":16685

Error from server (InternalError): error when creating "/scripts/issuer.yml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://diracx-de

logger=sqlstore.transactions t=2026-03-25T15:26:42.720237896Z level=info msg="Database locked, sleeping then retrying" error="database is locked" retry=0 code="database is locked"

{"time": "2026-03-25T15:26:19.592989+00:00", "msg": "Retrying (Retry(total=4, connect=9, read=5, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPCo

E0325 15:26:15.843697 1 authority.go:143] "cert-manager: error ensuring CA" err="secrets \"diracx-demo-cert-manager-webhook-ca\" already exists"

E0325 15:26:28.774826 1 setup.go:48] "cert-manager/issuers/setup: error getting signing CA TLS certificate" err="secrets \"root-secret\" not found" resource_name="diracx-ca-issuer" resource_name