ngless-toolkit / ngless-toolkit/ngless
NGLess should restart when using `parallel` and tasks are not finished
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 152
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the expectation is that the user will run ngless enough times, but that's not a great UI.
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
The issue names no files, tests, or entry points, so first map how parallel handles unfinished tasks and how repeated ngless runs currently resume work. Done means users no longer need to run ngless repeatedly when parallel tasks remain unfinished, with behavior covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100