temporalio / temporalio/sdk-ruby
[Feature Request] Warn on unawaited workflow futures with failures
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 204
- Forks
- 42
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 28
Description
Describe the solution you'd like
In Java workflows today, if a future that fails is never waited on, we warn on workflow completion. We should do the same in Ruby. Could even consider warning on futures that do not fail that are never waited on, but that may get annoying. There are several forms of this in the wild in several languages (JS, .NET, Python, etc), pick what is best.
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
No files, tests, or entry points are named. Compare the Ruby workflow-future behavior with the Java workflow warning described in the issue, then trace how Ruby observes futures at workflow completion; define the failure-only warning behavior and decide whether non-failing unawaited futures are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ruby
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100