关于“Connect Cloud Run Functions”的评价

Walter S. · 已于 over 1 year前审核

Ingrid L. · 已于 over 1 year前审核

John Benedict F. · 已于 over 1 year前审核

Sarah C. · 已于 over 1 year前审核

Rodel H. · 已于 over 1 year前审核

Patrick V. · 已于 over 1 year前审核

Bren A. · 已于 over 1 year前审核

John A. · 已于 over 1 year前审核

Amiel Z. · 已于 over 1 year前审核

Melvin T. · 已于 over 1 year前审核

P. T. · 已于 over 1 year前审核

Mark N. · 已于 over 1 year前审核

Kim Najima D. · 已于 over 1 year前审核

Maria Cristina C. · 已于 over 1 year前审核

Edwin S. · 已于 over 1 year前审核

Edwin S. · 已于 over 1 year前审核

g

David Z. · 已于 over 1 year前审核

Juliano F. · 已于 over 1 year前审核

Error try to connect to REDIS.

Rafael P. · 已于 over 1 year前审核

Sergio A. · 已于 over 1 year前审核

Akshat D. · 已于 over 1 year前审核

Mayra V. · 已于 over 1 year前审核

intéressant

franz l. · 已于 over 1 year前审核

As a standard practice with regards to using the active console/shell I open it in a separate tab. I do this because its easier to follow the execution results of the individual commands required from the lab. Also, it allows me to open multiple tabs whenever I encounter a long running command (e.g. deploy a new cloud function) and thereby continue the subsequent lab steps (setup a new folder for a cloud function and then deploy it also) while the initial active console/shell command executes to completion. However, I have noticed that I am frequently getting 'the connection to your Google Cloud Shell was lost' errors. Reconnecting to the active console after this error has the effect of opening a brand new shh session; all previous temporary and environment variables are wiped, including the gcloud project/region/zone config. All these variables need resetting before being able to continue with the lab. Its bad enough when this happens once or twice. When it happens three or more times it makes the lab almost unworkable. This is extremely frustrating. Why does the active console dropout like this? The amount of rework required to re-establish all the necessary variables makes any lab instruction that suggests validating your work e.g. by verifying a new VM/firewall instance has been created through the Console UI practically a death sentence for your active console. Why bother leaving your active console even for a few seconds when you have no trust that it will remain active until you get back? Especially when you need to spend another 5 mins setting your variables up again? Meanwhile the lab timer is constantly ticking down? I hope there is a way to review and rework this situation; it does not lead to a good experience at all.

Edward C. · 已于 over 1 year前审核

Nutullah K. · 已于 over 1 year前审核