Conversation
tekkaya
added this pull request to stack #12187
September 19, 2026 05:56
tekkaya
marked this pull request as ready for review
September 19, 2026 05:56
Contributor
|
Claude encountered an error after 3m 1s —— View job I'll analyze this and get back to you. |
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
1 participant
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.
What changed?
Lookup dynamic config for using chasm for nexus ops in workflows once for a batch of event applications.
Why?
Dynamic config for using chasm for nexus ops in workflows could be changed during a mutable state rebuild. Looking up the value once before the batch of event applications will direct the Nexus op schedule events consistently to either hsm or chasm.
How did you test it?
Potential risks
Low, we are reducing dynamic config lookup during mutable state rebuild into one and make the tree selection consistent.