You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed the issue in the `TestDictionaryCollections` test where clients that did not have the initial added target changes for server changes when running a host. Now, upon clients spawning players locally on the clients, the server write dictionary that is already populated by the host will have the added target changes injected during spawn to assure the changes match. (This is only for this specific test when running the host `TestFixture` pass.
AssertOnTimeout($"Client-{client.LocalClientId} add to server write collection property failed to restore on {className}{compDictionary.name}! {compDictionary.GetLog()}");
866
-
}
867
-
else// Host, for some reason, does not have changes tracked but the dictionaries match... ????
868
-
{
869
-
// TODO: Need to track down why host is the only failing test.
870
-
// NOTES: It seems only the host doesn't track changes made on the owner write permissions (i.e. issue with test itself?),
871
-
// but when comparing the values of the dictionaries everything passes (i.e. dictionaries are synchronized)
Assert.True(compDictionaryTest.ValidateInstances(),$"[Owner] Not all instances of client-{compDictionaryTest.OwnerClientId}'s {classNameTest}{compDictionaryTest.name} component match! {compDictionaryTest.GetLog()}");
882
-
Assert.True(compDictionaryServerTest.ValidateInstances(),$"[Server] Not all instances of client-{compDictionaryServerTest.OwnerClientId}'s {classNameTest}{compDictionaryServerTest.name} component match! {compDictionaryServerTest.GetLog()}");
AssertOnTimeout($"Client-{client.LocalClientId} add to server write collection property failed to restore on {className}{compDictionary.name}! {compDictionary.GetLog()}");
885
864
886
865
// Client-side add the same key and SerializableObject to server write permission property (would throw key exists exception too if previous failed)
0 commit comments