Roger Collins

Honestly, the project shouldn't be associated with Django at all, as it doesn't depend on Django, nor does it really have any Django-specific behavior from what I can tell.

The question is: why is it filling up space? This is happening with a default install, and nothing is actually using the cluster aside from itself.

Yep. I even tried changing all the topics to a 1GB retention as well, and it still fills up after a couple days.

I'm also a noob that ran into this problem. If you follow the guide.elm-lang.org word-for-word, you will run into this because you can't actually follow the instructions.

``` $ flux check ► checking prerequisites ✔ kubectl 1.20.4 >=1.18.0-0 ✔ Kubernetes 1.20.6+vmware.1 >=1.16.0-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.11.2 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v0.13.3...

Is there any workaround for this? This is a big stoppage for us. Can I manually install a CA into the source-controller?

How do you supply the replication factor for reply topics to work around this issue? topic_replication_factor=1 still results in the error.

It works fine for Keycloak v18: ``` @functools.cached_property def public_key(self) -> str: """Returns the Keycloak public key Returns: str: Public key for JWT decoding """ response = requests.get(url=self.realm_uri, timeout=self.timeout) public_key...

Yet another 3 year old issue that hasn't even been addressed.

I'm having this issue as well on 1.9.6. The problem is that I NEED the long lines to be processed.