temporalio / temporalio/temporal
deleteWorkflowExecution failure response leaks implementation details
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Actual Behavior
Calling DeleteWorkflowExecution in java-sdk for already deleted execution causes a response with the following message:
io.grpc.StatusRuntimeException: NOT_FOUND: operation GetWorkflowExecution encountered not found
Temporal server leaks implementation details of workflow execution deletion by oversharing that "GetWorkflowExecution encountered not found" while we didn't call GetWorkflowExecution, we called DeleteWorkflowExecution.
Reproduces on Temporal Cloud at 2022-09-20. Probably Temporal Server v1.17.6.
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 tracing the server-side handling of DeleteWorkflowExecution and the not-found response described in the issue. Reproduce the already-deleted execution case, then verify that the response identifies DeleteWorkflowExecution without leaking the internal GetWorkflowExecution operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100