temporalio / temporalio/features
Include structured command/event diff/items in non-determinism error
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
An explicit structure for "command event" type things should be defined in the sdk package of the API repo. Then we should have Go, Java, and Core emit a list of "expected" and "actual" "command event"s as serialized non-determinism error details.
Outstanding question: Is this error detail payload subject to failure conversion? If so, Core will have to go back through lang.
Per-SDK Tickets
- General design - TODO
- Go - TODO
- Java - TODO
- Core - TODO
- TypeScript - N/A
- Python - N/A
- .NET - N/A
- Ruby - N/A
- PHP - N/A
- 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 in the API repository's sdk package and review how non-determinism error details are represented. Resolve the outstanding failure-conversion question before defining the command event structure, then coordinate the Go, Java, and Core work. Done means the expected and actual serialized command events are emitted across the listed implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100