Repository navigation
Warn when http.get or http.head receive extra arguments - #5815
Merged
Merged
Conversation
moko-poi
requested review from
joanlopez and
szkiba
and removed request for
a team
April 8, 2026 03:46
moko-poi
force-pushed
the
warn-http-get-head-extra-args
branch
from
April 8, 2026 03:48
b7cdf6b to
77c21fa
Compare
moko-poi
temporarily deployed
to
azure-trusted-signing
April 8, 2026 07:52 — with
GitHub Actions
Inactive
moko-poi
temporarily deployed
to
azure-trusted-signing
April 8, 2026 07:54 — with
GitHub Actions
Inactive
Contributor
Author
|
@codebien Fixed the lll lint errors by splitting the long Warnf calls in http.get/http.head across multiple lines. PTAL ๐ |
moko-poi
temporarily deployed
to
azure-trusted-signing
April 8, 2026 13:31 — with
GitHub Actions
Inactive
moko-poi
temporarily deployed
to
azure-trusted-signing
April 8, 2026 13:33 — with
GitHub Actions
Inactive
Avoids flaky context deadline exceeded failures in TestComplicatedFileImportsForGRPC on Windows CI.
codebien
requested changes
Apr 8, 2026
| require.Empty(t, options.Validate()) | ||
|
|
||
| ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second) | ||
| ctx, cancel := context.WithTimeout(context.Background(), 15*time.Second) |
Contributor
There was a problem hiding this comment.
It doesn't sound the good approach, we should find a way to speed-up things here or even better make the test not time-dependent.
However, any change to address it, should live in a dedicated pull request. For this specific pull request we can just retry.
Contributor
Author
There was a problem hiding this comment.
@codebien Thanks for the feedback! You're right, I've reverted the timeout change. I'll retry the CI instead. If the flaky test needs a proper fix, I'll address it in a separate PR.
This reverts commit 22e22f3.
moko-poi
temporarily deployed
to
azure-trusted-signing
April 9, 2026 10:04 — with
GitHub Actions
Inactive
moko-poi
temporarily deployed
to
azure-trusted-signing
April 9, 2026 10:05 — with
GitHub Actions
Inactive
codebien
approved these changes
Apr 10, 2026
joanlopez
approved these changes
Apr 15, 2026
3 of 8 tasks
4 of 8 tasks
inancgumus
pushed a commit
that referenced
this pull request
May 15, 2026
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Emit a warning log when
http.getorhttp.headare called with more than 2 arguments (url + params).Why?
http.getandhttp.headonly accept(url, params), unlikehttp.postand other HTTP methods which accept(url, body, params). Users commonly writehttp.get(url, null, params)expecting the same 3-argument signature, which silently ignores the extra params. This warning helps users notice the mistake.Checklist
make check) and all pass.Related PR(s)/Issue(s)
Closes #2823