Function deployment always fails after 10 minutes
I've tried with github deploy now and it's the same situation
Anyone can help with this?
What's the output of docker ps -a right after failed build?
Hmm... The container isn't exiting...I wonder if it's really timing out....i know it takes like 5 minutes on cloud. It could be taking even longer on a lower spec machine
Is there anyway to verify that? Or only way is to increase RAM or CPU on the machine?
Anyone?
That depends on your provider. Usually they allow you to increase the specs on your VPS
There's no option to update RAM only so I tried a faster CPU, then the deployment finishes within 8 minutes without issue. So I'm guessing there must be a timeout set somewhere with _APP_FUNCTIONS_BUILD_TIMEOUT being ignored
Possible to look into this issue? The hosting costs are significantly higher with the faster CPU
What version of Appwrite do you have?
1.4.13
I looked through the code and it should be using that build timeout that defaults to 15 minutes. I'm not sure why it's ending at 10 minutes
I've tried to lower to 1 CPU with 1 GB RAM and deploy again, it ends at 10 minute mark again. But according to usage graphs RAM usage is just around 80% so doesn't seem like out of memory issue.
Can anyone help with the timeout issue?
Help how? Your server needs more resources
Help in fixing that itβs not using the correct timeout configuration? Iβm fine with longer deploying times but appwrite isnβt respecting the config value and terminating early.
Maybe there's something wrong with your function code so due to that it doesn't gets deployed?
If I use a better CPU to make it compile faster (less than 10 minutes) then it gets deployed without problem
The issue here is the environmental config value for deployment build timeout isnβt being respected.
Would you please create an issue?
for reproduction steps, you can put...
0. Ensure `_APP_FUNCTIONS_BUILD_TIMEOUT` is set to 900 (seconds)
1. Create a starter function
2. Update the build command to `sleep 720`
3. Create a deployment
@Triple Gelato have you had a chance to create the issue?
