events

I have this implemented in a custom marshaler now but wondering if it makes sense to push back upstream - when we are integrating with legacy services we find it useful to use the correlation ID as the message ID when first brought into watermill - from there they get sent on headers to subsequent services and work normally.

Its a simple change if it would make sense for other users.

Problem

Sugar Controller is a separate install, which makes its functionality less useful.

Similar to knative/serving#11969, remove sugar-controller as a separate installable YAML, and integrate it into the main eventing controller. Use a namespace-level label selector to enable and disable the sugar controller at the namespace level.

The [current documenta

Has anyone done this safely?

I'm submitting a ..

• Bug Report
• Feature Request

Current behavior:
The check for open? on a CFP uses Date.current.

Expected correct behavior:
This should use the current conference timezone.

Steps to reproduce:

1. Set a CFP end date
2. The the server to UTC
3. Set the timezone of the conference to somewhere else

Notice that during the time delta th