Skip to content

Backport CI fix #4492

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

Merged
merged 2 commits into from
Jul 5, 2023
Merged

Backport CI fix #4492

merged 2 commits into from
Jul 5, 2023

Conversation

dscho
Copy link
Member

@dscho dscho commented Jul 5, 2023

Seems that we're being hit by a test failure due to too-stringent assumptions on Git's part about cURL's error messages.

peff and others added 2 commits June 17, 2023 09:08
When redacting auth tokens in trace output from curl, we look for http/2
headers of the form "h2h3 [header: value]". This comes from b637a41
(http: redact curl h2h3 headers in info, 2022-11-11).

But the "h2h3" prefix changed to just "h2" in curl's fc2f1e547 (http2:
support HTTP/2 to forward proxies, non-tunneling, 2023-04-14). That's in
released version curl 8.1.0; linking against that version means we'll
fail to correctly redact the trace. Our t5559.17 notices and fails.

We can fix this by matching either prefix, which should handle both old
and new versions.

Signed-off-by: Jeff King <[email protected]>
Signed-off-by: Junio C Hamano <[email protected]>
* jk/redact-h2h3-headers-fix:
  http: handle both "h2" and "h2h3" in curl info lines
@dscho dscho self-assigned this Jul 5, 2023
@dscho dscho added this to the Next release milestone Jul 5, 2023
@dscho
Copy link
Member Author

dscho commented Jul 5, 2023

@dscho dscho merged commit e219204 into git-for-windows:main Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants