temporalio / temporalio/temporal
Ability to attach a local debugger to Local Temporal Worker
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
When testing a Temporal Worker locally, I would like the ability to expose a port and attach a debugger (either in a JetBrains product or VSCode) that allows me to trace each step the Worker takes. The debugging functionality provided by the Temporal Web UI is not sufficient in the slightest to trace where/why the application bugged out.
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
Start by defining how a locally running Temporal Worker should expose a debugger connection for JetBrains products or VSCode. Done means an attached debugger can trace each step of the Worker and provide more useful debugging than the Temporal Web UI.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100