temporalio / temporalio/features

Warn when activities dangle

Open
#501 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
32
Forks
28
Avg merge
1d 9h
Merged PRs (30d)
7

Description

Is your feature request related to a problem? Please describe.
Describe the solution you'd like

We're adding warnings when signals and updates dangle after the workflow closes or continues as new.
We should consider providing a similar warning when activities dangle.

Additional context
Per-SDK Tickets
  • Go -
  • Java -
  • Core -
  • TypeScript -
  • Python -
  • .NET -
  • PHP -
  • Temporal CLI -

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing warnings for dangling signals and updates, then check the per-SDK scope listed in the issue. Define the expected warning behavior for activities after a workflow closes or continues as new, with completion covering the applicable SDKs and Core behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, go, java, php, python, typescript
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.