fix: NetworkVariables with NetworkVariableUpdateTraits can cause other NetworkVariables to drop changes (up-port) #3466
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.
This PR resolves an issue where a
NetworkBehaviour
with multipleNetworkVariables
could drop changes if one of theNetworkVariables
has uniqueNetworkVariableUpdateTraits
set, is dirty, but is not ready to send.Based on user @khyperia's submission #3462.
Changelog
NetworkVariable
s on aNetworkBehaviour
could fail to synchronize changes if one hasNetworkVariableUpdateTraits
set and is dirty but is not ready to send.Testing and Documentation
NetworkVariableTraitsTests.WhenNonTraitsIsDirtyButTraitsIsNotReadyToSend
.Backport
This is an up-port of #3465