Josep Sampé

I started investigating this and seems that the problem is located in the runtime, and not in lithops itself. It needs further investigation, but for now what I did is...

@yuvipanda Good finding! I think PR #964 should be enough. You can test it using master branch

For now, in this initial step, `project_name`, `service_account `and `region` are still mandatory. https://github.com/lithops-cloud/lithops/blob/master/docs/source/compute_config/gcp_cloudrun.md#google-cloud-platform

@yuvipanda With #965 `project_name` and `service_account` are no longer required. `region` is still mandatory and I'm not sure if we can remove it: for now I don't see a way...

In the past we have been using Tekton for the Knative backend. We can explore AWS CodeBuild for AWS backends.

In principle we are not forcing 1200 seconds anywhere. May you have it in your config file? I just ran a test and the timeout is set correctly using master...

@ShuxinLin Unfortunately I'm not able to replicate your issue: ``` 2022-07-30 02:51:42,101 [INFO] config.py:131 -- Lithops v2.6.1.dev0 2022-07-30 02:51:42,428 [INFO] ibm_cos.py:98 -- IBM COS client created - Region: us-east 2022-07-30...

@sergii-mamedov Does #995 solve your issue?

@sergii-mamedov Fixed

#994 Should be enough to show the logs from the module_dependency.py at the same level set in Lithops