Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider suggesting turning off workflow cache for replay compatibility testing

Closed
  • Is something wrong?
#9 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

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.

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

Dominant language
No language data
Stars
230
Forks
31
Avg merge
2d 6h
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from temporalio/skill-temporal-developer

All issues in temporalio/skill-temporal-developer

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.