logviewer | A simple website used to view Modmail logs

Try to delete the ".buildozer" folder in your project folder, then edit your "buildozer.spec" file and add the requirements:

As already discussed in the comments the Ingress Controller will be created in the ingress-nginx namespace instead of the kube-system namespace. Other than that the rest of the tutorial should work as expected.

The problem is in the last return of data(), which should not return 0.

When returning 0, the view or its delegate(s) try to convert the value in a suitable type for that role, and since one of the first roles requested by a view is the size hint (and cannot convert your returned "0" to a valid size hint), the result is that it will not request any other data: since the size is invalid, the item is considered hidden, thus there's no need to ask for other roles.

Just remove the return 0 at the end of data(), as the implicit return is enough.

PS: the self.emit syntax you're using is considered obsolete, change that to self.numberPopulated.emit(itemsToFetch); also, explicit overloads are not required for signals that only have a single signature, so you can remove the ["QString"] from textChanged and [int] from numberPopulated.
I also suggest you to always leave at least a blank line between functions, as it makes your code much more readable.

TL;DR

In your storm.yaml, you need to add logviewer.cleanup.interval.secs: for the logviewer cleaner service to work. Restart the logviewer service afterwards.

Your question made me curious so I have done some digging, first through the storm docs, then through our cluster's logs, then through the storm source code.

Turns out the logviewer cleanup service does not have a default value configured and is initialized with null. This is not mentioned in the docs, however, examining our own logviewer logs, this line popped to my eye:

2020-12-10 13:34:42.129 o.a.s.d.l.u.LogCleaner main [WARN] The interval for log cleanup is not set. Skip starting log cleanup thread.

Looking through the default config file and the storm sources made it clear there is no default value configured and the process is initialized with null (this file, line 97), which actually does not start the cleanup service at all. Seems to me, that they forgot to mention that in their docs, so admins looking to configure the service would automatically set this.

After setting the value and restarting the logviewer, it immediately started cleaning the files, as I could see in the logs. So thanks for raising this question, it would have slipped my attention otherwise!

This is a community wiki answer. Feel free to edit and expand it if needed.

Nvidia GPU is not officially supported with the docker driver for Minikube. This leaves you with two possible options:

1. Try to use NVIDIA Container Toolkit and NVIDIA device plugin. This is a workaround way and might not be the best solution in your use case.

2. Use the KVM2 driver or None driver. These two are officially supported and documented.

I hope it helps.

Using the example for qi.logging from the docs, you can write the log messages to a file like so.