temporalio / temporalio/sdk-python
[Feature Request] Clarify exception on return type decoding failure
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
Describe the solution you'd like
Today in child workflow for instance if the return type is not the expected, it says "Failed decoding arguments". It should say "Failed to decode return value on ". Same for activities (and make sure it's clear what child/activity failed to encode if needed too).
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 locating the existing "Failed decoding arguments" exception text in the Python SDK and trace its child-workflow and activity return decoding paths. Exercise failures for child workflows and activities, including encoding failures where relevant; done means each message identifies the operation and clearly distinguishes return-value decoding from argument or encoding failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100