ngless-toolkit / ngless-toolkit/ngless
Better debug message for files missing for collect()
Open
Nobody has claimed this yet.
better error message
enhancement
- Dominant language
- Rust
- Stars
- 152
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
When using parallel, I've occasionally run into a situation where all locks are marked as .finished but collect() still reports Cannot collect (not all files present yet).
In this case it would be useful to know which samples are seen by NGLess as not present yet.
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
Search for the implementation of collect() and the parallel lock-handling path, starting with the error text "Cannot collect (not all files present yet)". Trace how missing files or samples are identified. Done means the debug message reports which samples are not present when collection cannot proceed; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100