lightninglabs / lightninglabs/taproot-assets
[feature]: worker pool that doesn't cancel workers on err
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
**Is your feature request related to a problem? Please describe.**
Spinoff off https://github.com/lightninglabs/taproot-assets/issues/527. Sometimes we need a worker pool that doesn't cancel all workers when one errs. Right now we implement this by sometimes only logging errors from workers but not propagating them. Ideally we would propagate without cancelling any workers,
**Describe the solution you'd like**
Alternative to `fn.ParSlice` with the above behavior.
**Describe alternatives you've considered**
Yeeting errors.
**Additional context**
Contributor guide
No contributing guide indexed for this repository
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 locating fn.ParSlice and tracing how it handles worker errors and cancellation. Define an alternative worker-pool path where errors are propagated without cancelling other workers, then add coverage showing workers continue after one returns an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100