command_timeout doesn't work?

[lesnoyleshyi]

Hi! Thanks for your action.
We are using it for about two years. From time to time we face an unexpected behaviour: scp action lasts more than hour to copy files when it's normally takes for about 2-3 minutes to do it. Size of our files is stable, it's about 350-400 Mb. This problem is always solved by rerun of the github workflow.
But the question is about command_timeout parameter. If it doesn't interrupt action after specified time, what it's intended for?

[vladelleus]

Hi!
I have the same problem, for some technical reasons the server where the application should be deployed was not working and the workflow was triggered due to some changes from devs. As a result the scp just stuck for 50 minutes in the copying state:

[appleboy]

I will take it.

[botaothomaszhao]

Hi!
I'm having the same problem too, the action took 10 minutes to 50 minutes to copy the file while it usually took about 1m.
When the action was stuck at line29 and coudn't reach 30, I check my server and found that .tar.gz file was already copied there, but it wasn't correctly untar till 50 minutes later. The timeout setting was at default. Hope that can help you!