Skip to content

[release-0.18] Backport #1083 #1113#1138

Merged
knative-prow-robot merged 3 commits intoknative:release-0.18from
navidshaikh:rel/v0.18.4
Nov 25, 2020
Merged

[release-0.18] Backport #1083 #1113#1138
knative-prow-robot merged 3 commits intoknative:release-0.18from
navidshaikh:rel/v0.18.4

Conversation

@navidshaikh
Copy link
Copy Markdown
Contributor

@navidshaikh navidshaikh commented Nov 25, 2020

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla Bot added the cla: no Indicates the PR's author has not signed the CLA. label Nov 25, 2020
@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 25, 2020
@navidshaikh
Copy link
Copy Markdown
Contributor Author

navidshaikh commented Nov 25, 2020

@BbolroC : can you please add your consent by adding comment @googlebot I consent. here ?

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

Comment thread hack/release.sh
Comment on lines +38 to +46
echo "🚧 Z Building for Linux(s390x)"
GOOS=linux GOARCH=s390x go build -mod=vendor -ldflags "${ld_flags}" -o ./kn-linux-s390x ./cmd/...
echo "🚧 🐳 Building the container image"
ko resolve --strict ${KO_FLAGS} -f config/ > kn-image-location.yaml
ARTIFACTS_TO_PUBLISH="kn-darwin-amd64 kn-linux-amd64 kn-windows-amd64.exe kn-image-location.yaml"
if type sha256sum >/dev/null 2>&1; then
echo "🧮 Checksum:"
sha256sum ${ARTIFACTS_TO_PUBLISH}
fi
ARTIFACTS_TO_PUBLISH="kn-darwin-amd64 kn-linux-amd64 kn-linux-arm64 kn-windows-amd64.exe kn-linux-s390x kn-image-location.yaml"
sha256sum "${ARTIFACTS_TO_PUBLISH}" > checksums.txt
ARTIFACTS_TO_PUBLISH="${ARTIFACTS_TO_PUBLISH} checksums.txt"
echo "🧮 Checksum:"
cat checksums.txt
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/cc @rhuss
PTAL

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@BbolroC
Copy link
Copy Markdown
Contributor

BbolroC commented Nov 25, 2020

@googlebot I consent

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

Copy link
Copy Markdown
Contributor

@rhuss rhuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
/hold

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 25, 2020
@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2020
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: navidshaikh, rhuss

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rhuss
Copy link
Copy Markdown
Contributor

rhuss commented Nov 25, 2020

Not sure why @googlebot still doesn't like it.

If everything breaks, I found out that if you squash the PR manually then you can get over this. However this will loose the history of the commit

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@rhuss
Copy link
Copy Markdown
Contributor

rhuss commented Nov 25, 2020

@BbolroC could you please comment @googlebot I consent. (mind the trailing dot, that you forgot on your fist comment). Thx!

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@BbolroC
Copy link
Copy Markdown
Contributor

BbolroC commented Nov 25, 2020

@googlebot I consent.

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

1 similar comment
@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@navidshaikh
Copy link
Copy Markdown
Contributor Author

@googlebot I consent.

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Nov 25, 2020

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@navidshaikh
Copy link
Copy Markdown
Contributor Author

@rhuss : looks like it commit has apparently another person as co-author whose github id no longer exists 🤔

@rhuss
Copy link
Copy Markdown
Contributor

rhuss commented Nov 25, 2020

@navidshaikh ok, in this case I suggest that you squash all commits locally on your branch and then force push it to this PR. That's the easiest way to overcome the CLA bot (which is stupid that he doesn't detect that these commits has been already consented in a different branch)

@navidshaikh
Copy link
Copy Markdown
Contributor Author

navidshaikh commented Nov 25, 2020

there are two separate emails @ gmail and @ ibm.com of @BbolroC which seems to confuse the bot

commit 44d9f14f9f96f35a6daeebd276cf3d1d8ed3e918
Author: Hyounggyu Choi <bbolroc@gmail.com>
Date:   Tue Nov 24 20:51:35 2020 +0100

    Cross-compile the kn binary for linux/s390x (#1083)
    
    Co-authored-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2020
@google-cla google-cla Bot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Nov 25, 2020
@navidshaikh
Copy link
Copy Markdown
Contributor Author

@rhuss : I edited the commit and reset its author to keep the history, ➜ client git:(44d9f14f) git commit --amend --reset-author
bot is happy now :-)

@BbolroC
Copy link
Copy Markdown
Contributor

BbolroC commented Nov 25, 2020

I will keep this in mind and never make the bot confused again. Thank @navidshaikh for the care.

* Fix a race condition between creating a watch and initiating the action that emits the event it is watching for

* update changelog

* add PR ID to changelog entry

* Fix merge in Changelog

* Fix table format in Changelog
@navidshaikh navidshaikh changed the title [release-0.18] Backport #1083 [release-0.18] Backport #1083 #1113 Nov 25, 2020
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 25, 2020
@knative-metrics-robot
Copy link
Copy Markdown

The following is the coverage report on the affected files.
Say /test pull-knative-client-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/eventing/v1beta1/client.go 85.8% 86.9% 1.1
pkg/serving/v1/client.go 64.5% 65.8% 1.3

@navidshaikh navidshaikh added the backport/pr A backport PR which is target to a release branch. label Nov 25, 2020
@rhuss
Copy link
Copy Markdown
Contributor

rhuss commented Nov 25, 2020

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2020
@navidshaikh
Copy link
Copy Markdown
Contributor Author

/unhold

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 25, 2020
@navidshaikh
Copy link
Copy Markdown
Contributor Author

/retest

    result_collector.go:75: ERROR: Error: Operation cannot be fulfilled on pingsources.sources.knative.dev "testpingsource0": the object has been modified; please apply your changes to the latest version and try again

@knative-prow-robot knative-prow-robot merged commit 0a8e53b into knative:release-0.18 Nov 25, 2020
mgencur pushed a commit to openshift-knative/client that referenced this pull request Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport/pr A backport PR which is target to a release branch. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants