temporalio / temporalio/skill-temporal-developer
Consider suggesting turning off workflow cache for replay compatibility testing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 220
- Forks
- 30
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 14
Description
Another common fix is turning off workflow cache during non-Go testing, thereby forcing replays to occur. Not sure if we should suggest this, would like to hear others' opinions.
Originally posted by @cretz in https://github.com/temporalio/skill-temporal-developer/pull/4#discussion_r2788631835
See references/core/common-gotchas.md
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 reading references/core/common-gotchas.md and the issue’s discussion about replay compatibility testing. Confirm with maintainers whether disabling workflow cache during non-Go testing should be recommended, then update that documentation if approved; the change is done when the guidance reflects the agreed decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100