-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
strict sphinx purview-workflow #36118
Conversation
API change check API changes are not detected in this pull request. |
) | ||
response = pipeline_response.http_response | ||
|
||
if response.status_code not in [200]: | ||
if _stream: | ||
await response.read() # Load the body in memory and close the socket |
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.
Is this now happening somewhere else?
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.
@iscai-msft do you know the reason for the change in the generated operations here?
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.
hmm that's interesting, let me take a look at this. We had removed this logic for stream-only operations, but I think this got overshot. Let me work on this today
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.
@annatisch @kristapratico @iscai-msft It is expected since _stream is always "False" therefore no need to judge it:
Context:
The logic is introduced in Azure/autorest.python#2628 and ever discussed here: Azure/autorest.python#2589 (comment) and Azure/autorest.python#2589 (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.
forgot to respond in this issue, but I believe this issue got resolved, is that correct @kristapratico?
Hi @kristapratico. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Hi @kristapratico. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing |
Resolves #33592