Open rszwajko opened 1 month ago
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
All actions that require fetching a big repository fail for me from time to time when triggered on slower/less stable internet connection. Moving closer to the WIFI router solves the problem in my case but for large scale deployments network bandwidth will always be a limiting factor. We should make the process more robust/optimized and/or provide a high level recovery (i.e. by re-starting an action).
The problem
The failure usually leaves logs similar to the following:
Please compare full logs from language discovery task on slow and fast internet (both for Nexus app). normal_internet.yaml.txt slow_internet.yml.txt
Improving the fetch process
Quick look at similar problems on StackOverflow suggests few approaches i.e. cloning a single branch with no history
On Nexus app this makes a big difference:
High level recovery
Right now user cannot directly restart the actions. Existing workarounds are not convenient:
The ideal solution would be to allow re-starting (or re-creating a new action with the same config) from the Task Manager.