chore: enable scheduler sentinel creation and chasm scheduler routing#10185
Merged
Conversation
The test exercises the V1 workflow-based schedule path but doesn't mock the CHASM scheduler client. With EnableCHASMSchedulerRouting defaulting to true, PatchSchedule routes to the CHASM path and nil-dereferences.
lina-temporal
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EnableCHASMSchedulerRoutingdefault totrue— schedule RPCs are now routed to the CHASM (V2) implementation first (with fallback to V1), excluding CreateSchedule.EnableCHASMSchedulerSentinelsdefault totrue— enables ID-space collision sentinels ahead of enabling CHASM scheduler creation.Why
Both of these flags need to be enabled if there are any chasm schedules on the cluster.