temporalio / temporalio/features
Tests to ensure dev-server/test-server processes properly shut down
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Today in many SDKs, you can start a dev server or time-skipping test server from the SDK and shut it down from the SDK. Various reports in various languages and across different OS/arch combinations are reporting that the process is not killed upon shutdown.
CI tests for all SDKs that have these subprocesses need to confirm that after shutdown the PID is gone.
Per-SDK Tickets
- Go - TODO (dev server only)
- Java - N/A
- Core - https://github.com/temporalio/sdk-core/issues/731
- TypeScript - TODO (need Core PID exposure first)
- Python - TODO (need Core PID exposure first)
- .NET - TODO (need Core PID exposure first)
- PHP - N/A
- Temporal CLI - N/A
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
Review the per-SDK checklist and the linked Core issue 731 first, then identify which SDK subprocesses need coverage. Done means CI tests confirm that the dev-server or time-skipping test-server PID no longer exists after SDK shutdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, typescript
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100