Skip to content
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

[5.0] Fix places where skip navigations are missed #22884

Merged
merged 1 commit into from
Oct 6, 2020

Conversation

ajcvickers
Copy link
Member

@ajcvickers ajcvickers commented Oct 4, 2020

Fixes #22882

Description

Skip navigations (i.e. many-to-many navigations; new for 5.0) are not being returned as members, navigations, or collections from an an API used to access them. In addition, scrubbing the code found three other issues with the same pattern, plus a few that need more investigation. This PR contains fixes and tests for the four clear issues. I have filed #22883 to follow up on the others.

Customer Impact

  • Navigations for a major new feature are not being returned from an API that should return them.
  • Attaching a graph asynchronously may miss navigations.
  • Skip navigations are missed as notification properties.
  • Exception will say a property is not found, when actually it is a navigation.

How found

Customer reported on RC2 daily build.

Test coverage

This PR adds tests for the affected cases, including others found from scrubbing the code. #22883 tracks doing more research in this area.

Regression?

No.

Risk

Low. The change only affects skip navigations, which are new in 5.0.

@ajcvickers ajcvickers requested a review from a team October 4, 2020 19:45
@ajcvickers ajcvickers added this to the 5.0.0 milestone Oct 4, 2020
Fixes #22882

**Description**

Skip navigations (i.e. many-to-many navigations; new for 5.0) are not being returned as members, navigations, or collections from an an API used to access them. In addition, scrubbing the code found three other issues with the same pattern, plus a few that need more investigation. This PR contains fixes and tests for the four clear issues. I have filed #22883 to follow up on the others.

**Customer Impact**

* Navigations for a major new feature are not being returned from an API that should return them.
* Attaching a graph asynchronously may miss navigations.
* Skip navigations are missed as notification properties.
* Exception will say a property is not found, when actually it is a navigation.

**How found**

Customer reported on RC2 daily build.

**Test coverage**

This PR adds tests for the affected cases, including others found from scrubbing the code. #22883 tracks doing more research in this area.

**Regression?**

No.

**Risk**

Low. The change only affects skip navigations, which are new in 5.0.
@ajcvickers ajcvickers merged commit 71063cb into release/5.0 Oct 6, 2020
@ajcvickers ajcvickers deleted the ThemNavsTooBertrum1004 branch October 6, 2020 14:51
@ajcvickers ajcvickers removed this from the 5.0.0 milestone Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants