[Feature][Config UI] Skipping Failed/Stalled Stages

[asterix314]

Search before asking

• [X] I had searched in the issues and found no similar feature requirement.

Description

The requested feature is an option to skip failed stages and carry on with the following stages in the pipeline, for those who have a long list of repos to run and want to make as much progress as possible in one go.

In "advanced mode", one can list tens or hundreds of stages(repos) in the "2D list" of the API, to run in sequence. But when one stage fails for whatever reason, the whole pipeline halts, missing the opportunity to run the following stages and just wasting time for human intervention.

Better still, a timeout (say 4 hours) setting can also be useful, for those stages that don't actually fail but still are not making any progress due to rate limiting etc.

Use case

Add a global option "skip stage when stalled", and a sub-setting for a timeout.

Related issues

No response

Are you willing to submit a PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[klesh]

@asterix314 Thanks for the feedback, it makes sense to me, @Startrekzky what do you think?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[Startrekzky]

@asterix314 Thanks for the feedback, it makes sense to me, @Startrekzky what do you think?

I'm not sure, may I know what specific problem happened while you were collecting data from multiple GitHub repos? Thanks. @asterix314

[asterix314]

@asterix314 Thanks for the feedback, it makes sense to me, @Startrekzky what do you think?

I'm not sure, may I know what specific problem happened while you were collecting data from multiple GitHub repos? Thanks. @asterix314

@Startrekzky I used the "2D list" API to collect a few hundred GitHub projects into DevLake. The stages ran in sequence. But when one stage fails, the whole pipeline stalls. There are many reasons for one stage to fail/stall:

• miss-spelt project names
• rate limit exceeded
• etc.

As a result, during the few days of the pipeline's execution, I found myself having to repeatedly return to the config-ui page to check if any stage failed and resume the pipeline manually. It would be much more efficient to automatically skip failed stages, and let the user intervene only at the end, when no executable stages are left unprocessed.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[Startrekzky]

@asterix314 Thanks for the feedback, it makes sense to me, @Startrekzky what do you think?

I'm not sure, may I know what specific problem happened while you were collecting data from multiple GitHub repos? Thanks. @asterix314

@Startrekzky I used the "2D list" API to collect a few hundred GitHub projects into DevLake. The stages ran in sequence. But when one stage fails, the whole pipeline stalls. There are many reasons for one stage to fail/stall:

• miss-spelt project names
• rate limit exceeded
• etc.

As a result, during the few days of the pipeline's execution, I found myself having to repeatedly return to the config-ui page to check if any stage failed and resume the pipeline manually. It would be much more efficient to automatically skip failed stages, and let the user intervene only at the end, when no executable stages are left unprocessed.

Thanks for the use case, I'll think about it.

[klesh]

1. allow users to skip failed tasks
2. allow users to rerun failed/succeeded tasks

[yumengwang03]

Ask me for the prototypes.

[mintsweet]

@yumengwang03 what does this retry-like button do?

[Startrekzky]

@mintsweet To rerun the subtask @mindlesscloud

[mintsweet]

@Startrekzky if I set up no skip failed task, can the task be rerun? (Does the rerun button show?)

[Startrekzky]

@Startrekzky if I set up no skip failed task, can the task be rerun? (Does the rerun button show?)

Yes