Vigith Maurice

Yes, I have assigned it to you.

@borkox With [idle source watermark](https://github.com/numaproj/numaflow/issues/633), you should be able to fix this (Numaflow 1.1 release). The ideal generic solution will be through early triggers, which will be possible via a...

Can you change https://github.com/th0ger/numaflow-issue-idle-watermark-has-larger-offset/blob/main/samplemapper/main.py#L10-L11 to add ```python if self.count % 5 == 0: messages.append(Message(keys=[], value=f"count={self.count}".encode())) else: messages.append(Message.to_drop()) ``` We expect at least one response.

> Also, if the framework really requires empty Messages to be filled with to_drop(), why doesn't the framework prevent empty messages or inject to_drop() automatically? The reason why we did...

> @vigith I have [updated](https://github.com/th0ger/numaflow-issue-idle-watermark-has-larger-offset/commit/6e8df3927b94f58fb382ee8e9ae9a9492d8d49fc) the example repo as requested, but it still keeps logging warning messages. Please try to run and reproduce it. I have a minor PR for...

related to #476

should `instance-id` be the numaflow version?

`cargo --fix edition`

Numaflow supports namespace level [installation](https://numaflow.numaproj.io/operations/installation/#namespace-scope).

We install the minimal CRD at the cluster level. Namespaces get the full spec. This way we can have different versions in different namespaces.