[Feature Request] Properly shutdown executors when done using them
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Start by reading hello_activity_threaded.py and hello_activity_multiprocess.py, focusing on how each executor is created and used. Update both samples so the executors are properly shut down when finished, then run the relevant samples to verify they complete cleanly without leaving executor work active.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Right now in hello_activity_threaded.py and hello_activity_multiprocess.py we are not properly shutting down the executors and we should be.
- Dominant language
- Python
- Stars
- 367
- Forks
- 121
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 11
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.
More from temporalio/samples-python
-
enhancement
temporalio/samples-python#254 · 1 comment · 1 assignee ·
-
enhancement
temporalio/samples-python#253 · 1 assignee ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
temporalio/samples-python#231 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/samples-python#192 · 2 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
temporalio/samples-python#191 ·
All issues in temporalio/samples-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100