Connect Cloud Run Functions Reviews

Tomasz S. · Reviewed больше 1 года ago

Walter S. · Reviewed больше 1 года ago

Ingrid L. · Reviewed больше 1 года ago

John Benedict F. · Reviewed больше 1 года ago

Sarah C. · Reviewed больше 1 года ago

Rodel H. · Reviewed больше 1 года ago

Patrick V. · Reviewed больше 1 года ago

Bren A. · Reviewed больше 1 года ago

John A. · Reviewed больше 1 года ago

Amiel Z. · Reviewed больше 1 года ago

Melvin T. · Reviewed больше 1 года ago

P. T. · Reviewed больше 1 года ago

Mark N. · Reviewed больше 1 года ago

Kim Najima D. · Reviewed больше 1 года ago

Maria Cristina C. · Reviewed больше 1 года ago

Edwin S. · Reviewed больше 1 года ago

Edwin S. · Reviewed больше 1 года ago

g

David Z. · Reviewed больше 1 года ago

Juliano F. · Reviewed больше 1 года ago

Error try to connect to REDIS.

Rafael P. · Reviewed больше 1 года ago

Sergio A. · Reviewed больше 1 года ago

Akshat D. · Reviewed больше 1 года ago

Mayra V. · Reviewed больше 1 года ago

intéressant

franz l. · Reviewed больше 1 года ago

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. · Reviewed больше 1 года ago