Local function execution results in HTTP 500 Error

Hi all,
I'm trying to develop a new function on my Ubuntu 24.04 machine running the latest version of docker. I've read through the documentation to install and intialize the CLI as well as performed a major upgrade this evening from 1.8.x to 1.9.6, step running migrations to get my instance running again, so that is to say I've done upgrades lately and everything appears to work.

however, after I've pulled all my functions down to my workstation and try to run them , ALL OF THEM return an HTTP 500 error, even the ones that are working just fine on my server. I've tried things like changing the port. changing the HTTP verb, visiting /ping, or the directory I'm running the "appwrite run functions command from" and this at least has me see the command update as I change the function but I still get the HTTP 500 error no matter what I do so I'm not sure where I go from here as looking at the logs for the container running my command doesn't really have any useful data.

any advice or suggestions would be MUCH appreciated.

https://discord.com/channels/564160730845151244/1314302555127414895/1538022598946852975

since you mention an upgrade from 1.8.x to 1.9.6, did you went on 1.9.0 and 1.9.5 to run the migrate command as well ?

And for the upgrade did you use the web installer, or was it more manual (copy/paste the compose) ? in case of manual, have you the right openruntimes-executor and the right envs for them ?

and last question, do you use S3 on your setup ?

what i'm thinking rn, is that maybe the migration process wasn't fully smooth, and so result in errors 500

I upgraded from 1.8 to 19.6 directly using the docker compose syntax. From there it told me to finish the upgrade in a web browser which I complete on the server hosting AW. I left things alone and the install completed. From there I had a bunch of server 500 errors which I researched down to migrations and that's when I used the docker compose exec syntax to step migrate my database from 1.9.0 to 1.9.6

I'm unaware of any openruntime requirements for for the upgrade so I haven't touched those. tell me more?

I do not use S3

Would it be prudent then to step through all the DB migrations from 1.8.1 (my previous version) to 1.9.6 to rule out any DB issues?

I've also notice new behavior from my AW instance where it's not complaining about "invalid origin" but nothing has changed other than me commenting out an nginx directive to return a 404 when requesting /console

it's more like it's needed to run the migrate command between versions

since you don't use S3, the openruntime should work fine

also could you share what the containers logs says (check all containers related to functions)
since you get 500 there should be some logs in the workers that says what went wrong

I don't believe this solved the issue. deleting the function dir, recreating it from console and then pulling it to my workstation still presents a 500 error and I am using v 27 of the CLI

and what does the containers logs says ?

see main chat, I discovered the server console spits out bad function templates but the cli is fine

but thank you very very much for sticking with this problem