Repository navigation
test(server): preserve settlement activation gate - #185
Merged
Merged
Conversation
Loading
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.
The settlement reactor test harness provided its deferred activation service only while constructing the reactor layer. With the current Effect layer behavior, the returned
starteffect then saw the default ungated service and performed a snapshot read before activation, failing the server test deterministically.Retain the harness dependency layer outputs so the returned reactor service runs with the supplied activation gate. The focused suite passes repeatedly and production behavior is unchanged.
Generated with GPT-5.6 in LastCode.