Thanks @mmoayyed, we are working on some infrastructure fixes for this right now.
We are also still experiencing this issue from Github actions.
Here some examples from our public repositories.
https://github.com/philips-labs/dct-notary-admin/actions/runs/202195860
https://github.com/philips-labs/dct-notary-admin/runs/949743679?check_suite_focus=true
Hi @tom, have you been able to make progress with timeout issues? It seems like they are more frequent now.
Had this pop up again today after it seemed fine for a while. Does it make any difference whether we use the bash script or the GitHub Action?
https://github.com/Midnighter/structurizr-python/runs/981730484?check_suite_focus=true
@mmoayyed, we released a new version of the GitHub Action which makes more attempts and shortens timeouts. Would you try that out and let me know?
@Midnighter, we do always recommend the bash script. What are you using or would you be able to post a link to a build?
Hi @tom, I did post a link right there. It’s just displaying the repo as a preview for some reason.
So you say I should use the bash script over the GitHub Action? Then why offer an Action at all?
I originally switched to the Action because of Windows but have found out in the meantime that I can force a bash shell on Windows, too. So it’s not a problem.
Thanks very much @tom. I switched to the new version as soon as I saw the update, and so far have not seen any timeout issues pop up. I will keep an eye over the next few days and will keep you posted in case something goes wrong.
Thanks again for your help and support!
Hi @Midnighter, looks like this was run before 1.0.13
. We prefer the bash script over the GitHub Action, because the Action is just a wrapper around the bash script. Are you running into issues with the new Action or are you comfortable with the bash script?
I’ll keep an eye on it and possibly switch to the bash script, thanks.