Add back some worker / workflow / server management functionality
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by reviewing the skill's current structure and the Temporal CLI workflows it is intended to teach. Define how the skill should list workers, inspect workflow status and executions, check health, extract errors, cancel workflows, and read results. Done means these management tasks are supported through the Temporal CLI rather than the removed operational shell scripts.
Written by the indexing model from the issue text.
Description
For now I have cut all the operational shell scripts, to reduce surface of this skill prior to shipping.
We should re-work this to instead teach the agent to use the Temporal CLI directly, such as for these uses:
- List workers for a workflow (e.g. to debug why workflow is stuck)
- Check workflow status (e.g. wait until its running)
- Check worker health
- List recent workflow executions (e.g. find workflow IDs)
- Extract workflow errors
- Cancel workflows
- Read workflow results
- Dominant language
- No language data
- Stars
- 230
- Forks
- 31
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from temporalio/skill-temporal-developer
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
temporalio/skill-temporal-developer#109 · 1 comment ·
Maintainers usually reply within 3 days
-
Improve Go Saga PatternPossibly taken @brianstrauch claimed this 13 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/skill-temporal-developer#68 ·
Maintainers usually reply within 3 days
-
Add tracing to observabilityPossibly taken @patbeqo claimed this 13 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
temporalio/skill-temporal-developer#63 · 1 assignee ·
Maintainers usually reply within 3 days
-
Add generalized metrics supportPossibly taken @patbeqo claimed this 13 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
temporalio/skill-temporal-developer#62 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
temporalio/skill-temporal-developer#54 ·
Maintainers usually reply within 3 days
All issues in temporalio/skill-temporal-developer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
maxrave-dev/SimpMusic#2649 ·
Maintainers usually reply within 2 days
-
product/backlog
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TencentBlueKing/bk-nodemgr#3645 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Objects.List treats versions=false (and similar flags) as truePossibly taken @andaaron claimed this today. Openpriority: p2 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/storage-testbench#829 ·
Maintainers usually reply within 2 days
-
[Bug]: memory provider treats 1:1 DMs as shared surfaces, so DM turns never receive reviewed recordsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
rlaope/oh-my-hermes#2088 ·
Maintainers usually reply within 1 day