temporalio / temporalio/features
Append some details to error messages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
For activity failure, application failure, child workflow failure, Nexus handler failure, Nexus operation failure, and timeout failure, we should append all non-"details" properties to the message. Java already does this for most, Go for some, other languages do not at all.
May need to discuss if this is something we want to do with application failure since it is user created. Java and Go do though.
Per-SDK Tickets
- Go - Already done for some fields/errors
- Java - Done for all but Nexus handler exception
- Core - N/A
- TypeScript - TODO
- Python - TODO
- .NET - TODO
- Ruby - TODO
- PHP - TODO
- Temporal CLI - N/A
Contributor guide
No contributing guide indexed for this repository
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 comparing how the Go and Java SDKs currently format activity, application, child workflow, Nexus handler, Nexus operation, and timeout failures. Then inspect the corresponding error-formatting entry points in each unchecked SDK, including the application-failure decision. Done means the agreed non-"details" properties are appended consistently across the remaining SDKs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, ruby, typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100