为Firebase设置Cloud Functions的超时不会在控制台中保留;这是一个错误吗? [英] Set timeout for Cloud Functions for Firebase does not persist in the Console; is this a bug?

查看:45
本文介绍了为Firebase设置Cloud Functions的超时不会在控制台中保留;这是一个错误吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

更新:我更新了问题,以反映我在问题正文中描述的内容以及当时发生的情况.这也说明了为什么我没有将Sanyam的回答标记为正确的原因.控制台中存在一个错误,该错误导致超时值短暂. @MichaelBleigh的回复是最相关的,让我知道问题何时解决.

Update: I updated the question, to reflect what I described in the body of the question, and what was happening at the time. It also justifies why I did not mark Sanyam's response as correct. There was a bug in the Console that was causing the timeout values to be ephemeral. @MichaelBleigh's response was the most pertinent, letting me know when the issue was resolved.

在某些情况下,我有一个Cloud Function需要运行超过默认的60秒超时.

I have a Cloud Function that needs to run past the default 60 second timeout in some edge-cases.

问题是,尽管可以在Google Cloud Developer Console的Cloud Functions部分中更改此值,但每次部署后它都会恢复为原始默认值.

The issue is, while this value can be changed in the Cloud Functions section of the Google Cloud Developer Console, it reverts to the original default after each deploy.

是否可以将更改保留在Firebase配置文件之一中?

Is there a way I can persist the changes to this setting, perhaps in one of the Firebase configuration files?

推荐答案

默认超时可以在此处更改 https://console.cloud.google.com/functions/list
select function> test function> edit> timeout

Default timeout can be changed here https://console.cloud.google.com/functions/list
select function >test function > edit > timeout

这篇关于为Firebase设置Cloud Functions的超时不会在控制台中保留;这是一个错误吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆