Worker functions stuck on "Fetched 0 functions..." due to corrupted messages in v1-functions queue

@Ibaraki Douji appwrite uses this openruntimes-executor right?

TL;DR

Developers are experiencing worker functions getting stuck on "Fetched 0 functions..." due to corrupted messages in v1-functions queue after upgrading to version 1.9.0. This bug causes the worker to be stuck in an infinite loop, failing to execute scheduled functions. The issue stems from a message format mismatch in how ScheduleFunctions and Func class send messages to the v1-functions queue. Restarting containers does not resolve the problem as the corrupted messages continue to regenerate. The root cause is the mixing of proper schedule messages and corrupted event messages in the queue. Solution: To address this issue, developers may need to await the forthcoming

ye but i don't see a worker-executions

🫠

ohhhhhhhhhhhhhh

ye so there might be an issue with the compose you used (that might need fix from appwrite team) you seams to be missing :

appwrite-worker-executions
appwrite-worker-screenshots
appwrite-task-interval all 3 containers are new in 1.9.0

my setup have all of thoses : -# yes i'm on kubernetes, but check the names and the AGE for the 3 new containers

but this time I used the web installer

okyyyy

then maybe there is an issue in there, i might look into it but if you can, try to add the worker executions from https://discord.com/channels/564160730845151244/1489440129553530980

docker-compose.yml in the appwrite docs has it?

these appwrite-worker-executions appwrite-worker-screenshots appwrite-task-interval

just checked, the web installer indeed have the issue and should be fixed for 1.9.1 installs (not yet available)

does not looks like it

Man I felt like i was some stupid for 4 daysssss

will try to make a hotfix for you, wait just a bit

Okyyyy

TypeScript

services:
  // ....
  appwrite-worker-executions:
    image: appwrite/appwrite:1.9.0
    entrypoint: worker-executions
    <<: *x-logging
    container_name: appwrite-worker-executions
    restart: unless-stopped
    networks:
      - appwrite
    depends_on:
      redis:
        condition: service_healthy
      mariadb:
        condition: service_healthy
    environment:
      - _APP_ENV
      - _APP_WORKER_PER_CORE
      - _APP_REDIS_HOST
      - _APP_REDIS_PORT
      - _APP_REDIS_USER
      - _APP_REDIS_PASS
      - _APP_ENV
      - _APP_DB_ADAPTER
      - _APP_DB_HOST
      - _APP_DB_PORT
      - _APP_DB_SCHEMA
      - _APP_DB_USER
      - _APP_DB_PASS
      - _APP_LOGGING_CONFIG

for the executions

and for the others two it's not in the github

so i need to convert from my k8s to a compose xdd

TypeScript

services:
  // ....
  appwrite-task-interval:
    image: appwrite/appwrite:1.9.0
    entrypoint: interval
    <<: *x-logging
    container_name: appwrite-task-interval
    restart: unless-stopped
    networks:
      - appwrite
    depends_on:
      redis:
        condition: service_healthy
      mariadb:
        condition: service_healthy
    environment:
      - _APP_ENV
      - _APP_WORKER_PER_CORE
      - _APP_POOL_ADAPTER
      - _APP_DOMAIN
      - _APP_DOMAIN_TARGET_CNAME
      - _APP_DOMAIN_TARGET_AAAA
      - _APP_DOMAIN_TARGET_A
      - _APP_DOMAIN_TARGET_CAA
      - _APP_DNS
      - _APP_DOMAIN_FUNCTIONS
      - _APP_DOMAIN_SITES
      - _APP_OPENSSL_KEY_V1
      - _APP_REDIS_HOST
      - _APP_REDIS_PORT
      - _APP_REDIS_USER
      - _APP_REDIS_PASS
      - _APP_DB_ADAPTER
      - _APP_DB_HOST
      - _APP_DB_PORT
      - _APP_DB_SCHEMA
      - _APP_DB_USER
      - _APP_DB_PASS
      - _APP_DATABASE_SHARED_TABLES
      - _APP_INTERVAL_DOMAIN_VERIFICATION
      - _APP_INTERVAL_CLEANUP_STALE_EXECUTIONS
  appwrite-worker-screenshots:
    image: appwrite/appwrite:1.9.0
    entrypoint: worker-screenshots
    <<: *x-logging
    container_name: appwrite-worker-screenshots
    restart: unless-stopped
    networks:
      - appwrite
    volumes:
      - appwrite-uploads:/storage/uploads:rw
    depends_on:
      redis:
        condition: service_healthy
      mariadb:
        condition: service_healthy
    environment:
      # Specific
      - _APP_BROWSER_HOST
      - _APP_WORKER_SCREENSHOTS_ROUTER
      - _APP_OPTIONS_FORCE_HTTPS
      # Basic
      - _APP_ENV
      - _APP_WORKER_PER_CORE
      - _APP_POOL_ADAPTER
      - _APP_LOGGING_CONFIG
      # Database
      - _APP_OPENSSL_KEY_V1
      - _APP_REDIS_HOST
      - _APP_REDIS_PORT
      - _APP_REDIS_USER
      - _APP_REDIS_PASS
      - _APP_DB_ADAPTER
      - _APP_DB_HOST
      - _APP_DB_PORT
      - _APP_DB_SCHEMA
      - _APP_DB_USER
      - _APP_DB_PASS
      - _APP_DATABASE_SHARED_TABLES
      # Storage
      - _APP_STORAGE_DEVICE
      - _APP_STORAGE_S3_ACCESS_KEY
      - _APP_STORAGE_S3_SECRET
      - _APP_STORAGE_S3_REGION
      - _APP_STORAGE_S3_BUCKET
      - _APP_STORAGE_S3_ENDPOINT
      - _APP_STORAGE_DO_SPACES_ACCESS_KEY
      - _APP_STORAGE_DO_SPACES_SECRET
      - _APP_STORAGE_DO_SPACES_REGION
      - _APP_STORAGE_DO_SPACES_BUCKET
      - _APP_STORAGE_BACKBLAZE_ACCESS_KEY
      - _APP_STORAGE_BACKBLAZE_SECRET
      - _APP_STORAGE_BACKBLAZE_REGION
      - _APP_STORAGE_BACKBLAZE_BUCKET
      - _APP_STORAGE_LINODE_ACCESS_KEY
      - _APP_STORAGE_LINODE_SECRET
      - _APP_STORAGE_LINODE_REGION
      - _APP_STORAGE_LINODE_BUCKET
      - _APP_STORAGE_WASABI_ACCESS_KEY
      - _APP_STORAGE_WASABI_SECRET
      - _APP_STORAGE_WASABI_REGION
      - _APP_STORAGE_WASABI_BUCKET