temporalio / temporalio/sdk-ruby
[Feature Request] Deadlock detection - improve interruption and stack trace
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 204
- Forks
- 42
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 28
Description
Describe the solution you'd like
Today, deadlocked workflow does not get interrupted and the stack trace is where we raised it. Try to interrupt the workflow if it is evicted post-deadlock and try to put the stack trace of the deadlocked thread as the deadlock error's stack trace.
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 by reading the workflow deadlock detection and eviction interruption paths, then trace how the deadlock error's stack trace is assembled. Done means an evicted deadlocked workflow is interrupted and the error reports the deadlocked thread's stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100