temporalio / temporalio/samples-dotnet

[Bug] temporal-sdk-dotnet process doesn't close if test is stopped during debug on Visual Studio 2022

Open
#88 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
114
Forks
42
Avg merge
4d 9h
Merged PRs (30d)
14

Description

What are you really trying to do?

Debugging unit test.

Describe the bug

During debug, If I stop before debug finishes on Visual Studio, temporal-sdk-dotnet-1.3.1.0.exe never closes / stops running.
In the video I show normal operation, that temporal-sdk-dotnet process starts and closes, if test finished normally.
On the second part of the video, I do it again, but stop the test execution before it finishes and temporal-sdk-dotnet never goes away.
If I run another test, It creates a new instance and it starts to acumulate multiple orphaned instances.
image

https://github.com/user-attachments/assets/5161ee0d-4988-40f8-8e07-d2a694a3dc80

Minimal Reproduction

Demo project to run
TemporalDemo - Copy.zip

Environment/Versions
  • OS and processor: Windows 11, x86
  • Temporal Version: temporal-sdk-dotnet-1.3.1.0
  • Are you using Docker or Kubernetes or building Temporal from source? None. Unit tests doesn't use those.

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 with the attached TemporalDemo - Copy.zip and reproduce the issue by stopping a unit test during debugging in Visual Studio 2022 on Windows 11. Compare normal completion with an interrupted test and verify that the temporal-sdk-dotnet-1.3.1.0.exe process is closed and does not accumulate orphaned instances.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.