ngless-toolkit / ngless-toolkit/ngless
Explicit way of invalidating locks
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 152
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes when I'm testing things, jobs fail and leave active locks behind.
Subsequent calls fail as they cannot obtain any lock.
Currently I workaround this by removing the ngless-locks folder or the matching subfolder inside ngless-locks which is suboptimal.
With that said, it would be nice if after:
ngless --options ... mycustomscript.ngl
one could:
ngless --clear-locks mycustomscript.ngl
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 at the ngless command entry point and trace how the existing lock directory is created and checked. Compare the requested ngless --clear-locks mycustomscript.ngl invocation with the current ngless --options ... mycustomscript.ngl flow; done means users can explicitly clear the relevant locks without manually removing ngless-locks directories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100