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

Set OperationId for incomplete LRO #44098

Merged
merged 7 commits into from
Jun 1, 2024
Merged

Conversation

live1206
Copy link
Member

Resolves #44097

@live1206 live1206 requested a review from a team as a code owner May 17, 2024 05:30
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

Copy link
Member

@jsquire jsquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before we add more functionality to this, I'd like to be sure that we restore AOT compatibility, which was inadvertently broken by the initial LRO rehydration PR.

Since this is shared source used by a wide array of libraries, this effectively renders any consumer with paging non-AOT compatible, which is an issue for those we have committed to being part of the ASP.NET Core critical path, such as KeyVault and Monitor.

see: #44127

If there is a critical need for this PR to merge, please let me know and we can work together on a plan to ensure that the AOT fixes are prioritized after this closes.

@live1206
Copy link
Member Author

@jsquire Given #44208 is merged, could you take another look at this?

@live1206 live1206 merged commit 4735e3a into Azure:main Jun 1, 2024
36 checks passed
@live1206 live1206 deleted the operation-id branch June 1, 2024 00:58
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.

[BUG] OperationId not set for incomplete LRO
5 participants