Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

fixed propagate publisher status and fixed the pubsubsecret #549

Merged
merged 1 commit into from
Feb 13, 2020

Conversation

capri-xiyue
Copy link
Contributor

Fixes #

Proposed Changes

  • fixed propagate publisher status
  • fixed empty pubsubsecret

Release Note


@knative-metrics-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/apis/events/v1alpha1/cloudschedulersource_validation.go 92.6% 92.9% 0.3
pkg/apis/events/v1alpha1/cloudstoragesource_validation.go 93.1% 93.3% 0.2
pkg/apis/pubsub/v1alpha1/topic_lifecycle.go 81.0% 60.7% -20.2

@nachocano
Copy link
Member

/lgtm
/approve

Thanks for the quick fix!

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: capri-xiyue, nachocano

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:
  • OWNERS [capri-xiyue,nachocano]

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

@nachocano
Copy link
Member

BTW, have you tried gcloud with storage and scheduler with these fixes and they work?
If so, then we should cherry-pick to 0.12.

@knative-prow-robot knative-prow-robot merged commit c7b801f into google:master Feb 13, 2020
@capri-xiyue
Copy link
Contributor Author

capri-xiyue commented Feb 13, 2020

BTW, have you tried gcloud with storage and scheduler with these fixes and they work?
If so, then we should cherry-pick to 0.12.

The gcloud create trigger works.

However, when I tried to send event, it doesn't work for all four sources.
I checked the logs of default-broker-ingress, the error logs is as follows:
{"level":"warn","ts":1581573877.5656204,"logger":"fallback","caller":"http/transport.go:510","msg":"got an error from receiver fn","error":"error sending cloudevent: 500 Internal Server Error"} {"level":"warn","ts":1581573877.5656753,"logger":"fallback","caller":"http/transport.go:602","msg":"error returned from invokeReceiver","error":"error sending cloudevent: 500 Internal Server Error"}

I don't think it's related to this PR. Maybe because I use the latest serving and eventing. Will investigate further tomorrow.

@nachocano
Copy link
Member

nachocano commented Feb 13, 2020 via email

@capri-xiyue
Copy link
Contributor Author

It looks like we also need to cherry-pick this PR cda1f5c. My PR is based on it.

@nachocano
Copy link
Member

nachocano commented Feb 13, 2020 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants