-
Notifications
You must be signed in to change notification settings - Fork 84
eng, add apply patches as post sdk-sync step #3178
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
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.
This file name change is not due to the adding of patches in "sync_sdk" apply_patches
Just my feeling that we'd better to make this file .patch too (instead of .diff).
| @@ -0,0 +1,2009 @@ | |||
| From 0c42d779a7065394e10a48d3985e81702eb754b3 Mon Sep 17 00:00:00 2001 | |||
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.
Curious how are those patch files generated? By agent?
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.
How other languages handle accepted header changes?
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 patches are generated by my reverts on SDK PR Azure/azure-sdk-for-java#46302
git format-patch -n 1 <sha>
At present, only .NET and Java has this "regen" step.
.NET has recording both on data-plane and mgmt-plane. On data-plane, they would let Redmond to solve. On mgmt-plane, they plan to update TestBase to let test-proxy ignore this header.
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.
Thanks! curious why do we change the generated sdk, instead of updating the recording to reflect the real sdk serialized headers?
Currently, these patches are to revert the changes to
acceptheaders on request without response body.