Behind the cover is a rocker switch that moves the seat, but it's not visible in this video.

It's extremely unlikely just "running into it" was the issue, but accidentally moving the seat in the wrong direction is somewhat plausible, especially if the cover is obscuring the switch.

It seems there's an expectation that ordinary ArgoCD users don't have (write) permissions to the cluster, and handling permissions is delegated to the checks you have on your git repos.

It does feel like a shortcut that limits the situations where ArgoCD can be used, but I can see how this could have been justified during the design process.

Because you can only have a single clustered index, you're effectively paying for efficient range queries on a single clustering key by making all other queries slower.

This tradeoff may or may not be worth it depending on your query patterns. In my experience, you can often get away with adding some subset of columns to a non-clustered index to make it covering, and get efficient range queries without making a copy of the entire dataset.

And even with clustered indexes, as soon as you want a range query that's not supported by your clustered index, you're faced with the exact same choices, except that you have to pay the cost of the extra B-tree traversals.

vscode doesn't let you split out the internal file explorer view, but the reverse is possible- you can quickly open any file in its own window, which can then be placed arbitrarily.

Many tiling window managers also allow you to group arbitrary windows into tabs.

    > As a trash talking AI, my primary function is to engage in witty and entertaining banter with users. My prompt is designed to guide me towards that type of conversation, with an emphasis on roasting, insult battles, and other forms of light-hearted humor. It also requires me to have a good understanding of pop culture, current events, and other relevant topics, in order to generate responses that are timely and relevant. Overall, this mode requires me to be quick-witted, adaptable, and able to respond in a way that is engaging and entertaining to users.

    > Sure, let me try to give some specific examples.

The primary key is included in all indexes, including non-clustered indexes, so in some cases there can be quite a large difference between UUID and integer PKs in terms of index size.

UUID PKs are also more susceptible to fragmentation.

I'll type the first few characters of a program installed on the machine, and the top result is the program I want.

But just as I hit Enter, the top result switches out to a web search, so instead of the program I wanted to start, I'm staring at a page of useless Bing results.

Just infuriating, and makes me so glad that I'm using Rofi/Wofi, which never changes the results without user input, and responds to keypresses with no perceptible delay, even when searching across every file in my home directory (via fzf).

> Where do you store volumes?

Back when it was a single node cluster, I just used hostFolder mounts with restic backups. I added Longhorn once the cluster grew, but there's still some local hostFolder mounts left around. For example, zigbee2mqtt needs to be on the node that has the zigbee controller plugged into it, so the node is tagged and zigbee2mqtt has a nodeSelector. This means the hostPath still works and I haven't needed to migrate it to Longhorn.

Longhorn initially scared me off with its relatively high listed resource requirements, but after configuring it to not run on the RPis it turned out to work quite well, most of the time just using a few percent CPU.

Use Tailscale for MagicDNS and access from any network.

Have a custom wildcard domain pointing to my tailscale k3s node ips, and a traefik ingress controller. This means exposing a service from my cluster on a subdomain just requires creating an ingress object in k3s, and it's only accessible via tailscale. cert-manager and let's encrypt handle TLS.

All services are deployed via gitops using ArgoCD, so changes are auditable and can be easily rolled back. Replacing hardware is just a matter of installing k3s and joining the cluster, then everything automatically comes up.

Restic for backups to s3.

For home automation I use a USB zigbee controller, mosquitto, zigbee2mqtt, room assistant, and home assistant, all deployed on k3s. These control my lights, HVAC, and various garage doors and gates. Also have mains-powered zigbee switches bound directly to devices so everything still works even if network or home assistant goes down.

The RPis are used for Room Assistant, which can automatically control lights/HVAC based on presence detection via a smartwatch. More intrusive actions (e.g. making lights brighter when already turned on, opening blinds) are pushed to the smartwatch for confirmation.

Grafana/prometheus to monitor sensors.

For media, jellyfin and sonarr/ radarr. The native Jellyfin app works very well on modern LG TVs.

Pihole to block ads on any device connected to Tailscale. Works globally.

Right now it's zero maintenance, and changes are automatically synced after a git push, so I almost never SSH into the servers directly.

  Ill Ill Ill Ill Ill

https://i.ibb.co/3mv1Myx/Ill.png

What a pleasing symmetry.

But right after seeming to acknowledge this, the author instead concludes that "even with a very poor performing ORM, the Database remains the primary time consumer".