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
'No TTL seen, dropping' when firing event manually for broker-trigger example #1392
Comments
I don't see a TTL attribute at https://github.com/cloudevents/spec/blob/master/json-format.md It looks like the attribute is called knativebrokerttl I tried adding a 'knativebrokerttl: 5' header but am still getting the same error. I notice the error message above mentions an attribute 'Knativebrokerttl: 255'. Perhaps it could be a case-sensitivity issue with the attribute matching (since the case on the first letter is a mismatch)? |
Is this related to #1421 |
/priority important-soon |
/assign mikehelmick |
…g, this attribute was changed to canonical mime encoding by the go http libraries. Fixes knative#1392 Fixes knative#1444
…g, this attribute was changed to canonical mime encoding by the go http libraries. Fixes knative#1392 Fixes knative#1444
I'm following the example at https://knative.dev/docs/eventing/broker-trigger/
In place of my-service I've deployed the event-display service. But it doesn't get that far. When I fire the CloudEvent it hits the broker which returns a 202. But it never hits the service and in the default-broker-filter logs I see this:
{"level":"warn","ts":"2019-06-12T15:25:39.969Z","logger":"provisioner","caller":"broker/receiver.go:133","msg":"No TTL seen, dropping","triggerRef":"default/event-display-trigger","event":"Validation: valid\nContext Attributes,\n cloudEventsVersion: 0.1\n eventType: dev.knative.foo.bar\n source: dev.knative.example\n eventID: 45a8b444-3213-4758-be3f-540bf93f85ff\n eventTime: 2018-04-05T03:56:24Z\n contentType: application/json\nExtensions,\n Knativebrokerttl: 255\nData,\n {\n "much": "wow"\n }\n"}
This 'No TTL seen' seems to be a failure condition but I'm struggling to see what could be wrong with the request as I've copied it directly from the example.
The text was updated successfully, but these errors were encountered: