sokrypton / sokrypton/ColabFold
Keep pending FOREVER
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2.9k
- Forks
- 747
- PR merge metrics
- No merged PRs in 30d
Description
When can ColabFold be fixed with continous Pending process as it used to?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the continuously Pending process described in the issue and review the current ColabFold execution path that handles job status. Trace where the process remains pending and compare it with the earlier behavior referenced by the report. Done means the cause is identified and the intended pending behavior is verified with a reproducible check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- bioinformatics, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100