Timeout is to short, or needs to be configured to monitor for running processes.
I have been trying to generate a listing of all of the blob sizes in a container, and it takes longer than the timeout settings and will not complete. If I run against a small container it works properly. Also, while it states I have been idle for 20 minutes I don't believe it was actually that long.
So is there currently no way to know what size each of my containers is?
I have a few containers totalling around the 2TB mark, so it takes more than 20 minutes for the Azure Cloud Shell to calculate each of their sizes. I would like to know how big each one is but I guess it's just impossible...
Tom J Sweet commented
Times out during the https://www.azuredevopslabs.com/labs/vstsextend/kubernetes/ tutorial
Reiji Saito commented
"Unset autologout" does not work.
Provisioning including "Application-Gateway" may take more than one hour in some cases.
The terminal session is disconnected even though the task of "Ansible-playbook" is being executed. . .
Aren't Microsoft developers too stupid to users?
Timothy Bruceruce commented
it was not running long at all then shut down lost connection
If I haven't touched a button on my remote while binge-watching Netflix, it'll ask "Are you still watching?" and will dump you to the menu if you don't answer yes after a few seconds.
Can we have Azure Cloud Shell ask if we're still working, rather than clearing the terminal? We may be referencing command output further back in the terminal buffer to troubleshoot a configuration issue and then it's all lost. At that point, I just quit the lab and go on to something else out of irritation.
This has been going on for almost 2 full years now and it has not changed? smh doubt it will at this point. Just very annoying when you have things to do while you wait. Takes about 5 minutes to create the VM which shaves time down to 15 min. Don't get distracted with life or blink too many times and its gone, timed out!. Thanks for the free service tho! Much appreciated!
timeout continues in 10 minutes, just changed the the message saying that 20 mins idle. please correct the information and timeout minimum 20 min, but it is really a short time, you should activate this parameter for each session, with a maximum in 1 hour.
Ed Gale commented
Teaching Microsoft Official workshops and would love to use Cloud Shell with students to speed up the process of doing labs. The 20 minute time out isn't enough, would be ok paying even for the compute to run the CLI at a longer time out than the free 20 minutes.
Alex Oehler commented
Why can't I set a timeout by myself?
Phil Morley commented
I'm lucky if I get a minute without it timing out, yet it says it's been idle for 20 minutes. MS definitely pulling my leg with this one, so frustrating
Craig N commented
Timing out after just 5 minutes or so. Saying "20 minutes" but it definitely isn't. Really frustrating. Can you tell me the fix please?
Windows 10 // Chrome
20 minutes is not long enough if you're working on a script. I keep getting timed out and have to start all over again running my test script. It almost makes this unusable for me.
Timeouts are way too short, shorter than 20mins after last activity.
paula critzas commented
some hacked my pc
Team, please address this issue soon, it's incredibly annoying!
Same experience here
Yes please! Console times out while I'm working through tutorials, please extend the timeout period.
some actions like deploying VPN Gateway may take more time:
"After running this command, it can take up to 45 minutes for the gateway configuration to complete." per https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-create-site-to-site-rm-powershell#CreateGateway
some of us lead busy lives. When I came back from taking care of my bed-ridden spouse, my VM was gone, and so was the security group. The timeout needs to be an hour minimum.
George Troughton commented
On Chrome on a MacBook Pro the Cloud Shell times out after two minutes.......... Not useable......