Selfhosted starter python function returns 500, starter node function works

I am running a selfhosted appwrite instance. Creating a node function and executing it works just fine but when i try to execute a python starter function, i get a "Error 500 An unexpected server error occured.".

I did not change anything about the runtimes or function env's in the .env file and its set up using the automated way (the only thing i changed was function and site domains)

Does anyone know why or how i can fix it?

Fixed it.

Problem 1: https://github.com/appwrite/appwrite/issues/11763 The docker compose file is simply broken and missing curcial services.

Problem 2: _APP_EXECUTOR_HOST (not sure on this, works like this for me) Apparently its set up wrong in the env file and needs to be _APP_EXECUTOR_HOST="http://openruntimes-executor/v1" There are multiple different "fixes" online, they name different hosts, like http://executor/v1, http://appwrite-executor/v1 etc.

The problem here is that the official .env var documentation doesnt say what the default should be, nor if we can figure it out ourself somehow.

Problem 3: The python starter template uses an sdk version thats not yet supportet (1.9.5) This needs to be adressed in the requirements.txt file (by hardcoding the 1.9.0 working version) or fix the template in line 22, changing context.log("Total users: " + str(response["total"])) to context.log("Total users: " + str(response.total))

<@&1319717958645452800> <@&634618551491100692>

Sorry for tagging you directly but i dont know who else to tag for this. Is this being looked into? There seems to be wrong A LOT for something that should "just work".

these issues as far as i know have been fixed in the latest codebase, they are just awaiting a new self hosted release

I know etas are annoying but do you have a rough timeframe as to when it might be done? Like, is it shortly deploying or are we more talking weeks/months?