Better stack trace upon `Parallel::DeadWorker`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 873
- Forks
- 164
- Avg merge
- 4d 27m
- Merged PRs (30d)
- 9
Description
When the parent process is killed during parallel execution the stack trace is unhelpful https://github.com/Shopify/tapioca/issues/1555. Can we extract the underlying trace?
At the very least if we can't find the trace we should suggest this could be a OOM issue and suggest --workers flag.
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 reading the linked tapioca issue 1555 and locating the handling for Parallel::DeadWorker in this repository. The work is complete when the error exposes the underlying stack trace when available, or suggests that an out-of-memory condition and the --workers flag may be involved when it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100