-
Notifications
You must be signed in to change notification settings - Fork 140
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
CORE-13335: Fix examples that assume invalid data cannot be ALIVE #645
CORE-13335: Fix examples that assume invalid data cannot be ALIVE #645
Conversation
Failure is not in my changes. The coherent_presentation example is broken:
|
The destination branch should be master, not develop, since this change is fine in the current Connext release. |
this is fixed in master. I've merged master into develop so it's now also fixed in develop. |
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.
Sync your repo and update destination branch.
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.
the commit brings unrelated changes to master (dynamic_data_skip_serialization)
Retarget to a branch other than master please. For example release/7.3.0 |
Can we create some guidelines as to what the target branches for this repo should be? I was following this task: #645 (comment) and it has held up the PR for weeks |
Creating a new PR since this one is a mess: #668 |
Summary
Update the keyed_data example that assumes that !valid_data means an instance cannot be ALIVE.
Details and comments
The introduction of Instance State Consistency means that a sample without valid_data can be in any instance state.
The following code is no longer correct:
Checks