temporalio / temporalio/sdk-java
Passing too large blob as an Activity input ends with non-descriptive gRPC error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Expected Behavior
If we pass a blob as an activity input that is larger than a server limit, we should get a descriptive message from the server about the failure and a clean Activity failure.
Actual Behavior
We get a broken gRPC channel.
Related user request:
while passing blob object into activity calls (say pdf or image files) I am getting the below exception
io.grpc.internal.AbstractClientStream$TransportState.inboundDataReceived Received data on closed stream
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 reproducing an Activity call with a blob larger than the server limit and inspect the resulting gRPC channel failure. Trace how the Activity input reaches the server and how the limit violation is reported; done means the caller receives a descriptive server message and a clean Activity failure instead of a broken channel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100