Opinie (Connect Cloud Run Functions)

Tomasz S. · Sprawdzono ponad rok temu

Walter S. · Sprawdzono ponad rok temu

Ingrid L. · Sprawdzono ponad rok temu

John Benedict F. · Sprawdzono ponad rok temu

Sarah C. · Sprawdzono ponad rok temu

Rodel H. · Sprawdzono ponad rok temu

Patrick V. · Sprawdzono ponad rok temu

Bren A. · Sprawdzono ponad rok temu

John A. · Sprawdzono ponad rok temu

Amiel Z. · Sprawdzono ponad rok temu

Melvin T. · Sprawdzono ponad rok temu

P. T. · Sprawdzono ponad rok temu

Mark N. · Sprawdzono ponad rok temu

Kim Najima D. · Sprawdzono ponad rok temu

Maria Cristina C. · Sprawdzono ponad rok temu

Edwin S. · Sprawdzono ponad rok temu

Edwin S. · Sprawdzono ponad rok temu

g

David Z. · Sprawdzono ponad rok temu

Juliano F. · Sprawdzono ponad rok temu

Error try to connect to REDIS.

Rafael P. · Sprawdzono ponad rok temu

Sergio A. · Sprawdzono ponad rok temu

Akshat D. · Sprawdzono ponad rok temu

Mayra V. · Sprawdzono ponad rok temu

intéressant

franz l. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu