-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model-based tests for PersistentShardCoordinator.State
#5974
Model-based tests for PersistentShardCoordinator.State
#5974
Conversation
…rdHomeAllocated` messages (akkadotnet#5967)" This reverts commit 4fa7abb.
Tried this with a complex configuration and the tests passed after several minutes.
No issues with the |
PersistentShardCoordinator.State
PersistentShardCoordinator.State
#5976 - must be merged first. |
@@ -35,5 +35,13 @@ public static class FsharpDelegateHelper | |||
value1 => { return Create<T2, T3, TResult>((value2, value3) => func(value1, value2, value3)); }; | |||
return FSharpFunc<T1, FSharpFunc<T2, FSharpFunc<T3, TResult>>>.FromConverter(conv); | |||
} | |||
|
|||
public static FSharpFunc<T1, FSharpFunc<T2, FSharpFunc<T3, FSharpFunc<T4, TResult>>>> Create<T1, T2, T3, T4, TResult>( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed to support 4 argument FSharp functions
Failing tests are all unrelated. |
We should backport this to 1.5 but it's not urgent cc @Arkatufus |
Fixes #5604
Changes
Added model-based test with FsCheck to validate that
PersistentShardCoordinator.State
is designed correctly.Checklist
For significant changes, please ensure that the following have been completed (delete if not relevant):