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.
thank u for helpful informtaion.to more information plz click https://www.trickcode.in/
Vatan Joshi commented
I have to start my from scratch every time just because of this. For me its not even staying 20 min active. This is too sad. I know you guys can do better.
I find cloudshell shuts down frequently due to 'inactivity' while I have a powershell script or terraform deployment running even when it has been running for <10mins and not for 20 mins like the timeout threshold is supposed to be. Please fix this asap as it needs to be robust for long running tasks and not just for running quick one off commands.
[Deleted User] commented
Alex Kolisnychenko commented
We're running "az vmss update-instances" command and it can take forever to finish, depending on the cluster size. 20 minutes is not adequate timeout for the shell.
this timeout is terrible. We are running a long script that creates Virtual Network Gateways so the timeout means we dont know how the script is progressing
Needful change, indeed very annoying when running comprehensive commands.
Trung Lai commented
Very annoying! Please increase the timeout or provide it as a configurable option.
Jamey Patterson commented
If you're in the middle of running a process that takes excess of the timeout period,
Is it possible to actually detect what is idle?
If not processing anything, actually idle, then timeout is fine.
But if you are waiting for a process to finish, please don't timeout.
Please increase timeout value to at least 1 hour.
Tab S commented
I also added this comment to another similar thread: Adding a configurable timeout length would be great. But at least if it is possible for Microsoft to extend the timeout, please extend it to at least an hour. I have created scripts that automate deployment of a lot of resources that altogether takes up to that long to complete (it includes creating and setting up an API Management Service, which by itself takes more than 20 minutes). And we have a need to use the Cloud Shell for this for 2 reasons: multiple people would have access to the script files and the platform, and success of the deployment is not dependent on a particular user's system. We need this for the sake of regulation and compliance.
I've been booted out after 10 minutes despite not actually being idle. 1/2 way through typing a command in and bang. see ya. start again please.
Very very very frustrating.
Oleh Romanchuk commented
Well, it's just frustrating, timed out during terraform deployment. It's just too buggy so far.
As a workaround, I'd suggest trying VSO https://online.visualstudio.com (worked for me)
Also, I'm going to try out tmux + some key-stroke generating script and see if it helps.
Regardless of the time out issue, I have a suggestion/request. It'll we very useful if you could make disown work in azure cli.
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.