Conectar o Cloud Run functions avaliações

Tomasz S. · Revisado há over 1 year

Walter S. · Revisado há over 1 year

Ingrid L. · Revisado há over 1 year

John Benedict F. · Revisado há over 1 year

Sarah C. · Revisado há over 1 year

Rodel H. · Revisado há over 1 year

Patrick V. · Revisado há over 1 year

Bren A. · Revisado há over 1 year

John A. · Revisado há over 1 year

Amiel Z. · Revisado há over 1 year

Melvin T. · Revisado há over 1 year

P. T. · Revisado há over 1 year

Mark N. · Revisado há over 1 year

Kim Najima D. · Revisado há over 1 year

Maria Cristina C. · Revisado há over 1 year

Edwin S. · Revisado há over 1 year

Edwin S. · Revisado há over 1 year

g

David Z. · Revisado há over 1 year

Juliano F. · Revisado há over 1 year

Error try to connect to REDIS.

Rafael P. · Revisado há over 1 year

Sergio A. · Revisado há over 1 year

Akshat D. · Revisado há over 1 year

Mayra V. · Revisado há over 1 year

intéressant

franz l. · Revisado há 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. · Revisado há over 1 year