I have made too many projects in my lifetime, and thought that a repository is not enough to handle support for them. I also believe that to be able to dump my mind from time to time keeps myself on track. I make projects because I like to help people with problems that may or may not be an issue, now or in the future.
This is not related to the homelab itself, but specifically to Proxmox and passthrough of hardware. I, as mostly everyone, have been for years been using Windows on a PC to play games. This have worked very great, but for the past 5 years (or more), M$ have been doing some shading things and design decisions that have made me want to move from them. The problem is that I am both unsure how gaming on Linux works, and if it will work for a bunch of games that I play daily.
I finally took an hour of my time and went through all active, and some inactive, services that I run, giving them relatively random names. This way I can separate servers from services. Each server had 5-6 places to change for the name to take effect. I then spent way too long time to figure how to modify the DNS through Ansible to link the service names to each server. The first issue was that I did not find a way to write this without having issues with duplicate CNAMEs.
While I was working to improve my homelab, I found it odd that single-name hostnames worked for Linux, but not for Windows (unless adding a punctuation at the end). As I’ve worked with DHCP before I’ve also seen the term “search domain” and wondered what it really does. In fact, it is used to tell clients to also add a suffix for a search domain. For example if your search domain is example.
Apparently for some odd reason, it is close to impossible to use apostrophes inside input files for complex filters, as ffmpeg hates this. I’m not sure why, and I’ve tried several ways to replicate it through bash, but the only way was to put quotes around the input file itself. The reason for this is still unknown, so I opt for a temporary solution by creating a temporary symbolic link to the input file and try it that way.
I managed to reduce the total time to 14 times native by integrating thread_local for Lua states. I will probably stop pursuing this further as now I probably need to micro optimize Lua the integration itself. Could be that as it does not output correctly would be a potential reason why it is slower too.
Worth noting is that the Lua rendering is not completely implemented as it currently does not work with blending.
Of course I would think that adding Lua as a rendering pipeline would reduce performance significantly, but I never imagined it would be to such degree. On Christmas and New Years holidays I had some free time I wanted to spend on a side project, just seeing how it would turn out. As mentioned previously, I started with creating the library loading and all the utility features around that, which was surprisingly both easy and straightforward.
Some should know by now that I have been thinking to add some sort of pipeline or add-on system used for the rendering. The rendering pipeline itself is currently set in stone, where you can only specify what parts to include and it will be done in proper order. I later thought of adding some sort of pipeline string where you can customize this, but I don’t expect people to find it intuitively enough.
One usually forgets the most useful tools right after using them. While I was refactoring a couple of months ago, I had done around 40 commits this day and suddenly realized that it did not render properly. As I had no idea what had caused this, i found out about git bisect. You give it two commit hashes, the first and the last, and it will binary search through all those commits, where you compile and test for each one, and tell if the bug exists or not on that specific commit.
The single most important thing with a thesis is the research question. It spans over the whole paper and binds every section together. It doesn’t need to be short, but it needs to be precise and clear.
I wrote this question in my introduction, but it is a bit rough, so I need to re-specify it. Normally you should write a research question and go from there, but it is more common that you have a general idea of what you want to research, and change the question along the way.
It is pretty late mention this, but it may help understanding how my workflow goes and how each tool interact with each other. A tool should be used to help the workflow, but also reduce the time it takes to do one or more tasks.
LaTeX is subjectively one of the best markup languages to create documents, slides, and whatnot. It takes time to learn it, but once you have used a template and get hang on references, figures, bibliography, etc, you will find it really powerful and efficient.