temporalio / temporalio/sdk-ruby
[Feature Request] Look into client-side trimming of failures to avoid server-side wrap-and-truncate
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 204
- Forks
- 42
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 28
Description
Describe the solution you'd like
Today if failure proto is too large server side, they truncate it and wrap in server error. See if there's something we can do client side before the failure is sent to limit its size. Probably needs to be opt-out too since server-side failure size limits can be customizable for self-hosted users.
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 how the Ruby SDK sends an oversized failure proto to the server. Determine where client-side size limiting could occur and how an opt-out would account for customizable self-hosted server limits. Done means oversized failures are handled client-side without unwanted server wrapping, while preserving an opt-out path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100