temporalio / temporalio/temporal
Timeout on complete when invalid task token passed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
The client should throw an exception immidiatley
Actual Behavior
Calling activityCompletionClient.complete with an invalid task token, gives a timeout after a while instead of an error.
Steps to Reproduce the Problem
workflowClient.newActivityCompletionClient().complete(
"bogus".toByteArray(), ""
)
- Timeout occurs after a while with the following exception:
Caused by: io.grpc.StatusRuntimeException: UNKNOWN: unexpected EOF
Specifications
- Version: v1.20.0
- Platform: amd64
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 at the activityCompletionClient.complete entry point shown in the reproduction and trace how an invalid task token is handled through the client and service. Reproduce the call with "bogus".toByteArray(); done means it fails immediately with an exception instead of timing out with an unexpected EOF.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- api, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100