-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Merge v2 into master #1731
Merge v2 into master #1731
Conversation
As previously attempted on v1, so it shall be on v2. We want to minimize the public API surface to more easily allow changes that won't break users.
ADOPTERS.md is modeled after the OPA ADOPTERS.md: https://github.com/open-policy-agent/opa/blob/master/ADOPTERS.md
The token belongs to a user with no membership anywhere, and it is limited to only reading github packages.
Replace with internal copy of CamelCase
… parameters (#1267) * Added function nestedQueryParams with map[string] parameter for keeping track of and detecting circular references. Added test TestMessageToQueryParametersRecursive for testing gracefully handling of circular references between messages. See issue #1167 * Code-review change requests accepted * More missed circle references changed to cycle Fixes #1167
* httpbody in stream * httpbody contenttype in stream response * compare content type in test * Update examples/internal/integration/integration_test.go Co-authored-by: Johan Brandhorst <[email protected]> * httpbody readme update Co-authored-by: Johan Brandhorst <[email protected]>
Use half of the Circle runners resources.
All unary and streaming error responses are now handled with a single function each, and are configured in a single place.
Codecov Report
@@ Coverage Diff @@
## master #1731 +/- ##
==========================================
+ Coverage 53.38% 58.74% +5.36%
==========================================
Files 42 33 -9
Lines 3902 3624 -278
==========================================
+ Hits 2083 2129 +46
+ Misses 1562 1237 -325
- Partials 257 258 +1
Continue to review full report at Codecov.
|
Everything else is now green except CLA for @kentdotn and @odsod. Manual check by entering the username also gives me a red warning. Kent, did you use the exact same username to submit the CLA? FTR the emails that PR tool sees are |
I've signed the CLA just now - should be all good on my end! |
I believe the issue is that PR #1446 had a For @odsod in PR #1504, there was an The new patches in this PR have different addresses for some reason? I'll file this as an edge case that could be supported. |
@googlebot please be nice and recheck (though I fully expect you'll fail). I'd like to let authors of the bot take a look at this by Tuesday afternoon GMT, and after that I'll flip the flag manually. The CLAs were in place when the PRs were submitted (the bot said so!), the authors said they've signed CLAs here in this thread, hence it's reasonable to proceed with "this is fine". |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@kentdotn Looks like your registration with the gmail.com address has Github username Can you fix the username? I'm told you may need to revoke and re-sign your CLA. If you're asked about the username, make sure you enter just |
@googlebot I fixed it. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@googlebot I consent. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
2 similar comments
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@ivucica I've changed |
@kentdotn It's actually all green on CLA bot's side. Your change did the trick. What I don't understand is why, despite all signals being green, the final result is still 'needs author consent'. I'll file a new bug. @googlebot run the check again, please. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
I'm flipping the bit. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
Draft change of merging v2 into master. Probably have to freeze
v2
andmaster
from now until I can merge this. I'm going to come back to this and update things that are missing/incorrect before we can make the release.Fixes #1223