Skip to content

Conversation

@yycptt
Copy link
Member

@yycptt yycptt commented Dec 23, 2025

What changed?

  • Do a final staleness check after reload

Why?

  • Due to data loss or force failover, it's possible that even after reload the mutable state may still be stale.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@yycptt yycptt requested a review from dandavison December 23, 2025 22:36
@yycptt yycptt requested review from a team as code owners December 23, 2025 22:36
@yycptt yycptt requested a review from dandavison January 5, 2026 18:33
Copy link
Contributor

@dandavison dandavison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this. Code is much cleaner now.

@yycptt yycptt merged commit c897bdc into temporalio:main Jan 6, 2026
59 checks passed
@yycptt yycptt deleted the chasm-final-staleness-check branch January 6, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants