-
Notifications
You must be signed in to change notification settings - Fork 183
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
Failed to execute Update-GitHubIssue #7621
Comments
@weshaggard , do you know why this issue doesn't happen in eng sync pipeline? Powershell version is same as 7.4, the only difference I noticed is the OS type. Go pipeline uses Ubuntu while eng sync pipeline uses windows server 2022. We also tested against windows OS locally which ended up with the same error. |
I cannot open the teams link for some reason. Can you directly link the failing build so I can have a look? I know that the new PS version has started rolling out to our pipelines and it has causes some encoding issues. |
It appears that the definition of ContentType was changed in pwsh 7.4 |
@weshaggard content-type has to be set explicitly. Please review the PR which works for pwsh 7.4 and the previous version. |
Pretty sure this has been fixed by @weshaggard already. |
I believe this was fixed by #8275 |
It was successful before, but it's a problem now.
Update-GitHubIssue: https://github.com/Azure/azure-sdk-for-go/blob/main/eng/common/scripts/Invoke-GitHubAPI.ps1#L367
pipeline failure link: https://teams.microsoft.com/l/message/19:b76b7ede-5516-43b4-96c2-f580fa4309d7_eaa95837-fda2-47de-949f-654b6771e436@unq.gbl.spaces/1706860464853?context=%7B%22contextType%22%3A%22chat%22%7D
local test:
curl: (successful)
pwsh Invoke-RestMethod:
Failure: The given key 'Content-Type' was not present in the dictionary.
we ran this test locally using latest powershell 7.4.1.
Adding Content-Type in Headers was successful (Content-Type: "application/json")
The text was updated successfully, but these errors were encountered: