[Feature Request] Increase amount of error information in output from failed updates and queries
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 379
- Forks
- 103
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Description
See https://github.com/temporalio/cli/pull/642#discussion_r1735366421
Note, this update error may contain lots of valuable information beyond just the message appended to "unable to update workflow: ". It may have details, causes, etc. Don't need to solve now (not solved for query either), but we should probably open an issue to provide a better dump of failure upon failure. Same for start update where a validator could provide details. I think for workflow execute we dump the entire close event.
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 reviewing the linked discussion in PR #642, especially the notes about update and query errors. Trace the CLI paths for failed updates, queries, and start-update validation, then define completion as exposing the available error details, causes, and other failure information rather than only the appended message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100