Skip to content

Conversation

@vincent-pli
Copy link
Contributor

Fixes #issue-number

Proposed Changes

The original image path is not work, will make the Revision failed and raise container missing error.

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Oct 10, 2019
@knative-prow-robot
Copy link
Contributor

Hi @vincent-pli. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow-robot knative-prow-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 10, 2019
- # This corresponds to
# https://github.com/knative/eventing-contrib/blob/release-0.5/cmd/event_display/main.go
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display@sha256:bf45b3eb1e7fc4cb63d6a5a6416cf696295484a7662e0cf9ccdf5c080542c21d
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should actually be s/eventing-sources/eventing-contrib/

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display
image: gcr.io/knative-releases/github.com/knative/eventing-contrib/cmd/event_display

- # This corresponds to
# https://github.com/knative/eventing-contrib/blob/release-0.5/cmd/event_display/main.go
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display@sha256:bf45b3eb1e7fc4cb63d6a5a6416cf696295484a7662e0cf9ccdf5c080542c21d
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display
image: gcr.io/knative-releases/github.com/knative/eventing-contrib/cmd/event_display

@vincent-pli
Copy link
Contributor Author

vincent-pli commented Oct 11, 2019

Thanks for comments, fixed according the comments.

Actually the image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display also could work, I get this url in another samples:
https://github.com/knative/docs/blob/master/docs/eventing/samples/sequence/sequence-reply-to-event-display/event-display.yaml

Do we need to fix that one to make consistent?

@RichieEscarez
Copy link
Contributor

Thanks for comments, fixed according the comments.

Actually the image: gcr.io/knative-releases/github.com/knative/eventing-sources/cmd/event_display also could work, I get this url in another samples:
https://github.com/knative/docs/blob/master/docs/eventing/samples/sequence/sequence-reply-to-event-display/event-display.yaml

Do we need to fix that one to make consistent?

Yes we should. I believe that URL only works because it was left up and available to avoid breaking the past docs. Now that "eventing-sources" repo has gone away and renamed to "eventing-contrib" we should only use "eventing-contrib" going forward. Thanks @vincent-pli

@vincent-pli
Copy link
Contributor Author

@RichieEscarez
Thanks for clarification, I search the repo, there are a dozen of these mistakes, will we change them all?

@RichieEscarez
Copy link
Contributor

@n3wscott can you help confirm that all the gcr.io URLs can simply be updated to /eventing-contrib/? There are 22 instances of "eventing-sources" in our repo.

@RichieEscarez RichieEscarez added kind/eventing-contrib ok-to-test Indicates a non-member PR verified by an org member that is safe to test. triage/needs-eng-input Engineering input is requested and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 21, 2019
@samodell samodell removed the triage/needs-eng-input Engineering input is requested label Jan 16, 2020
@samodell
Copy link
Contributor

/approve
/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samodell, vincent-pli

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

The pull request process is described here

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

@knative-prow-robot knative-prow-robot merged commit 64a2507 into knative:master Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants