-
Notifications
You must be signed in to change notification settings - Fork 65
fix issue with none current page responses #30
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
Conversation
|
@schaabs, |
Codecov Report
@@ Coverage Diff @@
## master #30 +/- ##
==========================================
- Coverage 88.33% 88.22% -0.11%
==========================================
Files 10 10
Lines 1140 1138 -2
==========================================
- Hits 1007 1004 -3
- Misses 133 134 +1
Continue to review full report at Codecov.
|
|
Hi @schaabs LGTM, but current_page is not supposed to be None. Ever. Could you share how you end up with this issue? Might worth adding a unittest. |
|
Currently the azure key vault service returns null as a value when responding to a get on collections with no items. Our C# and Java clients are tolerant to this and simply don't iterate. However in python we raise a type error when we len(self.current_page) since current page is None. Ideally this will be fixed on the service side, but I'm proposing this fix to unblock python keyvault clients in the meantime. Let me know what you think. Below is an example call from the keyvault python sdk tests which demonstrate this problem: |
RandalliLama
left a comment
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.
![]()
No description provided.