-
Notifications
You must be signed in to change notification settings - Fork 166
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
Fix compile error when Azure SDK is targeting .NET 6. #2245
Conversation
Thank you for your contribution @AraHaan! We will review the pull request and get back to you soon. |
cc: @annelo-msft for reviews. |
I have made changes above to use the ReadOnlyMemory version of WriteAsync where the framework provides it for Stream when it implements .NET Standard 2.1. Since Core > 2.1 implements it and that the Azure SDK targets .NET Framework, Standard 2.0, Core 3.1, and now .NET 6 I think it should be fine after this. |
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.
These are Azure.Core types, one of @christothes, @JoshLove-msft, or myself will need to approve them. @AlexanderSher, @jsquire FYI.
This should be ready for review, just waiting on when you all have time to review. |
Hi @AraHaan. 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. |
Still working on this. |
cc: @annelo-msft any thoughts on anything else that may cause compile errors when targeting .NET 6 on the Azure SDK (before this gets merged and we find that there was some that were missed)? |
Thank you @AraHaan for your contribution, let me ping @christothes, @AlexanderSher, @annelo-msft, @JoshLove-msft , @m-nash @jsquire . |
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.
I have made the requested changes. |
@AraHaan Sorry for the late response. This PR is different after a series of changes. I have a question: why Is there any benefit to use |
The former still compiles for programs not set to warn as error, but it generates Visual Studio warnings about using the span versions instead of them (and if warnings as error is enabled it ends up emitting errors instead). Also, I think the span ones are a smidge faster as I think the ones without span end up calling into the span ones which could waste at least a few cpu clock cycles when using .NET 6+ (or even the .NET versions that have the span versions of them). |
github automatically removed the other pending reviewers ^. |
@AraHaan branch is out of date with feature/v3 can you please sync to the latest so the CI can run and validate? |
/azp run autorest.csharp |
Azure Pipelines successfully started running 1 pipeline(s). |
I wish I could see why that smoketest is failing. |
@AraHaan Normally it's due to timeout:
I've restarted the failed task. |
/azp run autorest.csharp |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Changes are fine but branch still says out of date with feature/v3 which will block merge
/azp run autorest.csharp |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
When I tried to do Azure/azure-sdk-for-net#28911 which basically adds .NET 6 to the .NET Azure SDK, it resulted in compile errors due to the code in this repository. As such this change is a prerequisite of that pr.
Checklist
To ensure a quick review and merge, please ensure:
Ready to Land?