关于“Connect Cloud Run Functions”的评价

Tomasz S. · 评论over 1 year之前

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之前