There could be an issue where TaskDriver Systems get configured to write to a Task Driver data stream.
In the event that there is more than one TaskDriver, the System job will only actually write to the first Task Driver that exists. This will lead to data loss or false responses in the first Task Driver.
What is the current behaviour?
There is nothing to prevent this error, so you could shoot yourself in the foot.
What is the new behaviour?
A check runs to make sure that this doesn't happen and throws and exception.
What issues does this resolve?
None
What PRs does this depend on?
None
Does this introduce a breaking change?
[x] Yes - If you were breaking this rule, you will now get an error and need to update your jobs.
[ ] No
Tag-Alongs
Changed ENABLE_UNITY_COLLECTIONS_CHECKS to ANVIL_DEBUG_SAFETY as per #139
There could be an issue where TaskDriver Systems get configured to write to a Task Driver data stream. In the event that there is more than one TaskDriver, the System job will only actually write to the first Task Driver that exists. This will lead to data loss or false responses in the first Task Driver.
What is the current behaviour?
There is nothing to prevent this error, so you could shoot yourself in the foot.
What is the new behaviour?
A check runs to make sure that this doesn't happen and throws and exception.
What issues does this resolve?
What PRs does this depend on?
Does this introduce a breaking change?
Tag-Alongs
ENABLE_UNITY_COLLECTIONS_CHECKStoANVIL_DEBUG_SAFETYas per #139