StackStorm / StackStorm/orquesta
Naming a workflow task "get_task" causes "'TaskSpec' object is not callable" error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 111
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
If any task in the task list is named "get_task", "has_task", or various other variations visible in https://github.com/StackStorm/orquesta/blob/b8109939b0c4ace374a42a2b5e6161a3c07b5349/orquesta/graphing.py#L78, the workflow will fail at runtime with an opaque error as seen above.
Possible resolution: use internal or hidden naming for properties of WorkflowGraph objects, or store tasks within a dictionary property of WorkflowGraph objects so that name collisions with workflow tasks can not occur or are unreasonable to accidentally discover
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
Start with the task-name handling in orquesta/graphing.py around line 78 and reproduce the runtime failure using a task named "get_task" or "has_task". Trace how WorkflowGraph properties collide with workflow task names, then verify that these names no longer produce the opaque "TaskSpec" callable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100